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

skill-router-mcp

by anujkumar8076
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

get_skill

Retrieve a skill's full SKILL.md instructions, capped at 8000 tokens. If truncated, returns sections to fetch remaining parts individually.

Instructions

Load a skill's full SKILL.md instructions (capped at 8000 tokens). If truncated is true, fetch the remaining parts one at a time with get_skill_section using the returned sections list.

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>"
    },
    "name": "get_skill"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesSkill name as returned by list_skills or match_skill

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.5/5.0
Behavior4/5

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

With no annotations provided, the description carries full burden. It discloses truncation behavior, token cap, and the returned sections list. It does not mention side effects, but as a read operation, this is adequate.

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?

Two focused sentences with no wasted words. Essential information is front-loaded: what it does, the token cap, and conditional behavior for get_skill_section.

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

Completeness5/5

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

For a simple tool with one parameter and no output schema, the description fully explains input (skill name) and output behavior (full instructions or truncated with sections). Completely adequate for an agent.

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

Parameters4/5

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

Schema coverage is 100%, and the description adds value beyond the schema by explaining token cap and truncation handling. The parameter description in schema is clear, and the tool description enriches context.

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 loads a skill's SKILL.md instructions with a token cap, and distinguishes it from get_skill_section by specifying when to use the latter for truncated content.

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

Usage Guidelines4/5

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

It explicitly tells when to use get_skill_section if truncated, providing clear context. However, it does not explicitly say when not to use this tool or mention alternatives like list_skills or match_skill.

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