Skip to main content
Glama
Sign In
skill-router-mcp

skill-router-mcp

by anujkumar8076
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

get_skill_section

Fetch a specific H2 section from a large skill by heading name to avoid truncation. Get precise content when the full skill was truncated.

Instructions

Fetch a single H2 section of a skill by heading name. Use for large skills where get_skill returned truncated: true.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "name": "<name>",
      "section": "<section>"
    },
    "name": "get_skill_section"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesSkill name
sectionYesH2 heading to fetch (case-insensitive; substring ok)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description must cover behavioral traits. It implies a read operation but does not disclose idempotency, error handling, or what happens if the section is not found. It lacks depth beyond the basic action.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is two sentences, front-loading purpose and usage guidance without any fluff. Every sentence contributes essential information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given simple parameters and no output schema, the description adequately explains what the tool does and when to use it. However, it does not describe the return format or contents of the section, which would be helpful for an agent to process the output.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Both parameters are described in the schema (100% coverage), so the description adds minimal extra meaning. The phrase 'by heading name' aligns with the section parameter but does not provide new details beyond the schema's own descriptions.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool fetches a single H2 section of a skill by heading name, using specific verbs and resources. It also distinguishes from siblings by mentioning the truncated scenario, making the purpose unmistakable.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly states when to use this tool: 'Use for large skills where get_skill returned truncated: true.' This directly guides the agent to choose this over get_skill or other siblings in that context, with no ambiguity.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools