synapse-router

classify_task_complexity

Computes a deterministic complexity score and recommends a model tier for an agent step, so you can route prompts to cost-appropriate models before execution.

Instructions

Compute deterministic complexity score [0.0, 1.0] and recommended model Tier (FAST_LOCAL, BALANCED, FRONTIER_REASONING) for an agent step.

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": {
      "prompt": "<prompt>"
    },
    "name": "classify_task_complexity"
  }
}

Input Schema

Name	Required	Description	Default
`prompt`	Yes
`tools_schema`	No
`system_prompt`	No
`latency_sla_ms`	No
`require_json_schema`	No
`estimated_output_tokens`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.1.0Nov 12, 2026

TDQS

C2.9/5.0

Behavior3/5

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

With no annotations, the description carries the full behavioral burden and does disclose that scoring is deterministic and that Tier can be FAST_LOCAL, BALANCED, or FRONTIER_REASONING. However, it does not explain what factors drive the score, whether the call is pure/cheap, or how the optional parameters alter behavior.

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 definition is a single front-loaded sentence with no filler or repetition. It delivers the core output contract efficiently, though its brevity contributes to gaps elsewhere rather than being a structure problem.

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?

The tool has six parameters, nested objects, no annotations, and no output schema, but the description is only one sentence. It conveys the output range and Tier names, yet leaves parameter semantics and much of the scoring behavior undocumented, making it incomplete for the tool's complexity.

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% across six parameters, yet the description explains none of them. It does not add meaning for prompt, tools_schema, system_prompt, latency_sla_ms, require_json_schema, or estimated_output_tokens, so an agent gets no semantic guidance beyond structural schema fields.

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

Purpose4/5

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

The description states a specific verb ('Compute'), resource ('deterministic complexity score and recommended model Tier'), and scope ('for an agent step'). It is clear what the tool does, though it does not explicitly differentiate itself from siblings such as route_agent_step.

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

Usage Guidelines2/5

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

The description gives no explicit when-to-use or when-not-to-use guidance and names no alternatives. Use is only implied by the phrase 'for an agent step', leaving the agent to infer whether this should be called before routing or elsewhere.

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

Deploy Server