Docs: Tool router

[Sushmithamallesh]

Note

Adds Tool Router docs (overview and usage guide), updates navigation, and includes a TypeScript quickstart snippet.

• Docs: Tool Router
  • New pages:
    • pages/src/tool-router/overview.mdx: feature overview, core concepts, quick example, next steps.
    • pages/src/tool-router/using-tool-router.mdx: prerequisites, session creation examples, connection management.
  • Code snippet: snippets/tool-router/quickstart.ts (TypeScript session creation example).
  • Navigation: updates fern/docs.yml to add Tool Router section with tool-router/overview and tool-router/using-tool-router.

^{Written by Cursor Bugbot for commit 0e88172. This will update automatically on new commits. Configure here.}

[claude]

Claude finished @Sushmithamallesh's task —— View job

---

Documentation Review for Tool Router

I've completed a comprehensive review of the Tool Router documentation changes focusing on grammar, spelling, clarity, readability, consistency, and adherence to the documentation style guide.

Todo List:

• Read fern/CLAUDE.md style guide
• Review fern/docs.yml navigation changes
• Review fern/pages/src/tool-router/overview.mdx
• Review fern/pages/src/tool-router/using-tool-router.mdx
• Review fern/snippets/tool-router/quickstart.ts
• Provide comprehensive feedback and recommendations

Review Findings

Navigation Changes (docs.yml)

✅ Good: Moved Tool Router from "(Experimental)" to main section, making it more discoverable
✅ Good: Changed "Getting started" page path from getting-started.mdx to using-tool-router.mdx which is more descriptive

Overview Page Issues

Grammar & Spelling:

• Line 19: "Has isolated Auth configurations that is scoped" → should be "are scoped"
• Line 23: Missing article - "muliple services" → "multiple services"

Style Guide Adherence:

• Line 2: Title "Tool router overview" should follow title case: "Tool Router overview" (capitalize Tool Router as it's a product name)

Content Issues:

• Line 18: Missing period at end of sentence "Has its own unique MCP server endpoint"
• The experimental note is good but consider making it more prominent with a Warning callout instead of Note

Using Tool Router Page Issues

Grammar & Spelling:

• Line 23: "muliple services" → "multiple services"
• Line 33: "outloook" → "outlook"
• Line 57: Missing article - "For this you will need to create an auth configuration" → "For this**,** you will need to create an auth configuration"

Style Guide Issues:

• Line 3: Subtitle should be more descriptive than just "Create a tool router session"

Content & Structure:

• Line 111: File ends abruptly with empty lines - incomplete content
• Section titles could follow better progressive disclosure (start simple, add complexity)
• Missing cross-links to authentication documentation (mentioned but not properly linked)

TypeScript Snippet

✅ Good: Clean, well-structured code example
✅ Good: Proper imports and realistic variable names
✅ Good: Good use of comments

Recommendations

High Priority Fixes:

1. Fix spelling errors: "muliple" → "multiple", "outloook" → "outlook"
2. Fix grammar: "configurations that is scoped" → "configurations that are scoped"
3. Complete the using-tool-router.mdx file (ends abruptly)
4. Fix title case for "Tool Router overview"

Medium Priority Improvements:

1. Consider using Warning callout for experimental status to make it more prominent
2. Add proper cross-links to authentication docs
3. Improve subtitle in using-tool-router.mdx to be more descriptive
4. Add missing punctuation (periods, commas)

Low Priority Enhancements:

1. Consider reorganizing sections to better follow progressive disclosure principle
2. Add more context about when NOT to use Tool Router

Overall Assessment

The documentation provides good coverage of the Tool Router feature with clear examples. The structure follows logical flow from overview to implementation, and the TypeScript code snippet is well-written. However, several grammar and spelling issues need attention, and the using-tool-router.mdx file appears incomplete. Once these issues are addressed, this will be solid documentation for the new feature.

---

[github-actions]

Preview your docs: https://composio-preview-3ec0d454-1e52-4090-9004-365d057eaf52.docs.buildwithfern.com

[claude]

Claude finished @Sushmithamallesh's task —— View job

---

Documentation Review for Tool Router

I've completed a comprehensive review of the Tool Router documentation changes focusing on grammar, spelling, clarity, readability, consistency, and adherence to the documentation style guide.

Todo List:

• Read fern/CLAUDE.md style guide
• Review fern/docs.yml navigation changes
• Review fern/pages/src/tool-router/overview.mdx
• Review fern/pages/src/tool-router/using-tool-router.mdx
• Review fern/snippets/tool-router/quickstart.ts
• Provide comprehensive feedback and recommendations

Review Findings

Navigation Changes (docs.yml)

✅ Good: Tool Router properly structured in navigation with clear section hierarchy
✅ Good: Proper icon usage and slug configuration
✅ Good: Page titles are descriptive and follow hierarchy

Overview Page (overview.mdx)

Grammar & Spelling Issues:

• Line 19: "Has isolated Auth configurations that is scoped" → should be "that are scoped" (subject-verb agreement)
• Line 18: Missing period after "Has its own unique MCP server endpoint"

Style Guide Adherence:

• Line 2: Title "Tool router overview" should follow title case: "Tool Router overview" (per style guide: "Titles must always start with an uppercase letter, followed by lowercase letters unless it is a name")

Content & Structure:
✅ Good: Follows BLUF principle with clear introduction
✅ Good: Progressive disclosure from basic concept to technical details
✅ Good: Experimental note is appropriately placed
✅ Good: Logical flow from "What is" to "When to use" to "Core concepts"
✅ Good: Proper use of CardGroup for next steps

Using Tool Router Page (using-tool-router.mdx)

Critical Code Issue (Already identified by Cursor):

• Line 29: Missing await keyword - const session = await composio.experimental.toolRouter.createSession is correct, but there may be other instances missing await

Grammar & Spelling Issues:

• Line 23: "muliple services" → "multiple services" (spelling error)
• Line 25: "muliple toolkits" → "multiple toolkits" (spelling error)
• Line 33: "outloook" → "outlook" (spelling error)
• Line 57: Missing comma - "For this**,** you will need to create an auth configuration"

Style Guide Issues:

• Line 3: Subtitle "Create a tool router session" should be more descriptive following progressive disclosure principle

Content Issues:

• File ends abruptly at line 111 with empty lines - appears incomplete
• Missing cross-links to authentication documentation (referenced but not linked)
• Section structure could be improved to better follow progressive disclosure

TypeScript Snippet (quickstart.ts)

✅ Good: Clean, well-structured code example
✅ Good: Proper imports and realistic variable names
✅ Good: Good use of comments
✅ Good: Demonstrates key concepts clearly

Critical Issues to Address

High Priority:

1. Fix spelling errors: "muliple" → "multiple" (appears twice), "outloook" → "outlook"
2. Fix grammar: "configurations that is scoped" → "configurations that are scoped"
3. Complete the using-tool-router.mdx file (ends abruptly)
4. Fix title case: "Tool router overview" → "Tool Router overview"

Medium Priority:

1. Add missing punctuation (periods, commas)
2. Improve subtitle in using-tool-router.mdx to be more descriptive
3. Add proper cross-links to authentication documentation
4. Consider using Warning callout for experimental status to make it more prominent

Code Issue:

1. Verify async/await usage - Cursor identified a missing await that should be addressed

Overall Assessment

The documentation provides good coverage of the Tool Router feature with clear examples and logical structure. The content follows the style guide's principles of BLUF and progressive disclosure well. However, several spelling and grammar errors need immediate attention, and the using-tool-router.mdx file appears incomplete.

Strengths:

• Clear conceptual explanation
• Good use of code examples
• Proper experimental status communication
• Logical information hierarchy
• Effective use of documentation components

Areas for Improvement:

• Multiple spelling/grammar errors
• Incomplete content in usage guide
• Missing cross-references
• Title case consistency

Once the critical issues are addressed, this will be solid documentation for the new Tool Router feature.

---

[github-actions]

Preview your docs: https://composio-preview-54a299cb-03f8-43bc-a116-2a7d02d13a83.docs.buildwithfern.com

[claude]

Claude encountered an error —— View job

---

Documentation Review for Tool Router

I've completed a comprehensive review of the Tool Router documentation changes focusing on grammar, spelling, clarity, readability, consistency, and adherence to the documentation style guide.

Todo List:

• Read fern/CLAUDE.md style guide
• Review fern/docs.yml navigation changes
• Review fern/pages/src/tool-router/overview.mdx
• Review fern/pages/src/tool-router/using-tool-router.mdx
• Review fern/snippets/tool-router/quickstart.ts
• Provide comprehensive feedback and recommendations

Review Findings

Navigation Changes (docs.yml)

✅ Good: Tool Router properly structured in navigation with clear section hierarchy
✅ Good: Proper icon usage (route) and slug configuration
✅ Good: Page titles are descriptive and follow hierarchy

Overview Page (overview.mdx)

Grammar & Spelling Issues:

• Line 19: "Has isolated Auth configurations that is scoped" → should be "that are scoped" (subject-verb agreement)
• Line 18: Missing period after "Has its own unique MCP server endpoint"

Style Guide Adherence:

• Line 2: Title "Tool router overview" should follow title case: "Tool Router overview" (per style guide: "Titles must always start with an uppercase letter, followed by lowercase letters unless it is a name")

Content & Structure:
✅ Good: Follows BLUF principle with clear introduction
✅ Good: Progressive disclosure from basic concept to technical details
✅ Good: Experimental note is appropriately placed
✅ Good: Logical flow from "What is" to "When to use" to "Core concepts"
✅ Good: Proper use of CardGroup for next steps

Using Tool Router Page (using-tool-router.mdx)

Critical Code Issue (Already identified by Cursor):

• Line 29: Missing await keyword - const session = await composio.experimental.toolRouter.createSession is correct, but there may be other instances missing await

Grammar & Spelling Issues:

• Line 23: "muliple services" → "multiple services" (spelling error)
• Line 25: "muliple toolkits" → "multiple toolkits" (spelling error)
• Line 33: "outloook" → "outlook" (spelling error)
• Line 57: Missing comma - "For this**,** you will need to create an auth configuration"

Style Guide Issues:

• Line 3: Subtitle "Create a tool router session" should be more descriptive following progressive disclosure principle

Content Issues:

• File ends abruptly at line 111 with empty lines - appears incomplete
• Missing cross-links to authentication documentation (referenced but not linked)
• Section structure could be improved to better follow progressive disclosure

TypeScript Snippet (quickstart.ts)

✅ Good: Clean, well-structured code example
✅ Good: Proper imports and realistic variable names
✅ Good: Good use of comments
✅ Good: Demonstrates key concepts clearly

Critical Issues to Address

High Priority:

1. Fix spelling errors: "muliple" → "multiple" (appears twice), "outloook" → "outlook"
2. Fix grammar: "configurations that is scoped" → "configurations that are scoped"
3. Complete the using-tool-router.mdx file (ends abruptly)
4. Fix title case: "Tool router overview" → "Tool Router overview"

Medium Priority:

1. Add missing punctuation (periods, commas)
2. Improve subtitle in using-tool-router.mdx to be more descriptive
3. Add proper cross-links to authentication documentation
4. Consider using Warning callout for experimental status to make it more prominent

Code Issue:

1. Verify async/await usage - Cursor identified a missing await that should be addressed

Overall Assessment

The documentation provides good coverage of the Tool Router feature with clear examples and logical structure. The content follows the style guide's principles of BLUF and progressive disclosure well. However, several spelling and grammar errors need immediate attention, and the using-tool-router.mdx file appears incomplete.

Strengths:

• Clear conceptual explanation
• Good use of code examples
• Proper experimental status communication
• Logical information hierarchy
• Effective use of documentation components

Areas for Improvement:

• Multiple spelling/grammar errors
• Incomplete content in usage guide
• Missing cross-references
• Title case consistency

Once the critical issues are addressed, this will be solid documentation for the new Tool Router feature.

---

[github-actions]

Preview your docs: https://composio-preview-e3e18436-b661-479d-9a83-acbb096a3fbe.docs.buildwithfern.com

[claude]

Claude finished @Sushmithamallesh's task —— View job

---

Documentation Review for Tool Router

I've completed a comprehensive review of the Tool Router documentation changes focusing on grammar, spelling, clarity, readability, consistency, and adherence to the documentation style guide.

Todo List:

• Read fern/CLAUDE.md style guide
• Review fern/docs.yml navigation changes
• Review fern/pages/src/tool-router/overview.mdx
• Review fern/pages/src/tool-router/using-tool-router.mdx
• Review fern/snippets/tool-router/quickstart.ts
• Provide comprehensive feedback and recommendations

Review Findings

Navigation Changes (docs.yml)

✅ Good: Tool Router properly structured in navigation with clear section hierarchy
✅ Good: Proper icon usage (route) and slug configuration
✅ Good: Page titles are descriptive and follow hierarchy

Overview Page (overview.mdx)

Grammar & Spelling Issues:

• Line 19: "Has isolated Auth configurations that is scoped" → should be "that are scoped" (subject-verb agreement)
• Line 18: Missing period after "Has its own unique MCP server endpoint"

Style Guide Adherence:

• Line 2: Title "Tool router overview" should follow title case: "Tool Router overview" (per style guide: "Titles must always start with an uppercase letter, followed by lowercase letters unless it is a name")

Content & Structure:
✅ Good: Follows BLUF principle with clear introduction
✅ Good: Progressive disclosure from basic concept to technical details
✅ Good: Experimental note is appropriately placed
✅ Good: Logical flow from "What is" to "When to use" to "Core concepts"
✅ Good: Proper use of CardGroup for next steps

Using Tool Router Page (using-tool-router.mdx)

Critical Code Issue (Already identified by Cursor):

• Line 29: Missing await keyword - const session = composio.experimental.toolRouter.createSession should be const session = await composio.experimental.toolRouter.createSession

Grammar & Spelling Issues:

• Line 23: "muliple services" → "multiple services" (spelling error)
• Line 25: "muliple toolkits" → "multiple toolkits" (spelling error)
• Line 33: "outloook" → "outlook" (spelling error)
• Line 57: Missing comma - "For this**,** you will need to create an auth configuration"

Style Guide Issues:

• Line 3: Subtitle "Create a tool router session" should be more descriptive following progressive disclosure principle

Content Issues:

• File ends abruptly at line 111 with empty lines - appears incomplete
• Missing cross-links to authentication documentation (referenced but not linked)

Navigation Link Issue (Also identified by Cursor):

• Line 65 in overview.mdx: The href "/docs/tool-router/using-tool-router" doesn't match the actual slug configuration. Based on docs.yml, the correct path should be "/docs/tool-router-using-tool-router"

TypeScript Snippet (quickstart.ts)

✅ Good: Clean, well-structured code example
✅ Good: Proper imports and realistic variable names
✅ Good: Good use of comments
✅ Good: Demonstrates key concepts clearly

Critical Issues to Address

High Priority:

1. Fix spelling errors: "muliple" → "multiple" (appears twice), "outloook" → "outlook"
2. Fix grammar: "configurations that is scoped" → "configurations that are scoped"
3. Complete the using-tool-router.mdx file (ends abruptly)
4. Fix title case: "Tool router overview" → "Tool Router overview"
5. Fix missing await: Add await keyword in line 29 of using-tool-router.mdx
6. Fix broken navigation link: Update href in overview.mdx from "/docs/tool-router/using-tool-router" to "/docs/tool-router-using-tool-router"

Medium Priority:

1. Add missing punctuation (periods, commas)
2. Improve subtitle in using-tool-router.mdx to be more descriptive
3. Add proper cross-links to authentication documentation
4. Consider using Warning callout for experimental status to make it more prominent

Overall Assessment

The documentation provides good coverage of the Tool Router feature with clear examples and logical structure. The content follows the style guide's principles of BLUF and progressive disclosure well. However, several spelling and grammar errors need immediate attention, and the using-tool-router.mdx file appears incomplete.

Strengths:

• Clear conceptual explanation
• Good use of code examples
• Proper experimental status communication
• Logical information hierarchy
• Effective use of documentation components

Areas for Improvement:

• Multiple spelling/grammar errors
• Incomplete content in usage guide
• Missing cross-references
• Title case consistency
• Broken navigation link

Once the critical issues are addressed, this will be solid documentation for the new Tool Router feature.

---

[github-actions]

Preview your docs: https://composio-preview-1cfd523e-f84d-4815-a7f6-8cb95f5760c6.docs.buildwithfern.com