Skip to main content
Glama

ninerouter_model_info

Read-onlyIdempotent

Inspect the parameters and capabilities advertised for a model by ID to verify supported options and constraints before routing requests.

Instructions

Inspect the parameters and capabilities advertised for 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": {
      "id": "<id>"
    },
    "name": "ninerouter_model_info"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is fully covered there. The description adds essentially nothing beyond those flags — no indication of what happens for an unknown model id, whether results are cached, or whether 'advertised' capabilities reflect live provider data versus a static catalog.

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?

One short sentence with the verb front-loaded and no filler. It is efficient, but the brevity is bought at the cost of the missing usage and parameter detail rather than by trimming redundancy.

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?

There is no output schema, so the description carries the burden of conveying what an 'inspection' returns, and it says nothing about the shape — parameter list, context limits, capability flags, pricing. With zero-annotated schema coverage on the lone required parameter, the definition leaves an agent guessing about both input and output.

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

Parameters2/5

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

Schema coverage is 0% and the single required parameter 'id' is never described in the schema. The description only implies it is a model identifier through the phrase 'for a model'; it does not state the id format, whether it is a provider-prefixed slug, or how to obtain a valid one.

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?

States a specific verb ('Inspect') and resource ('the parameters and capabilities advertised for a model'), which reads as a per-model metadata lookup. It does not name the sibling it differs from (ninerouter_list_models), so the distinction from that enumeration tool must be inferred.

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 when-to-use guidance, no prerequisites, and no alternative named. An agent cannot tell from the text whether to call this or ninerouter_list_models first, or whether the model must exist in the account.

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