Skip to main content
Glama
Sign In
ModelRouter MCP

ModelRouter MCP

by MrSolution07
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

analyze_task

Analyze a plan document to identify task type, complexity, and requirement vector for advisory model selection guidance.

Instructions

Analyze a plan document for task type, complexity, and requirement vector. Advisory analysis only — does not select a model.

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": {
      "planPath": "<planPath>"
    },
    "name": "analyze_task"
  }
}

Input Schema

NameRequiredDescriptionDefault
planPathYes
repoPathNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3/5.0
Behavior2/5

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

No annotations are provided, so the description must fully disclose behaviors. It states the tool is advisory and does not select a model, but does not mention whether it is read-only, requires permissions, or has any side effects. Limited disclosure.

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

Conciseness4/5

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

The description is brief (two sentences) and front-loads the core purpose. However, it could be slightly more structured to include parameter details or output description.

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

Completeness2/5

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

No output schema exists, yet the description does not explain the structure or format of the analysis results. Combined with missing parameter explanations, the description is insufficient for proper understanding.

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

Parameters1/5

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

Schema description coverage is 0%, and the description does not explain the meaning or expected values of the parameters planPath and repoPath beyond their names. The agent lacks guidance on how to provide these inputs.

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 action ('Analyze a plan document'), the specific outputs ('task type, complexity, and requirement vector'), and distinguishes from siblings by noting it is advisory only and does not select a model.

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

Usage Guidelines3/5

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

The description implies usage for analysis rather than model selection, but does not explicitly state when to use this tool versus alternatives like recommend_model, nor does it provide conditions for when not to use it.

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