Skip to main content
Glama

ninerouter_chat

Run a 9Router chat or vision model by choosing the API dialect and passing its native request fields, letting MCP clients send prompts and get completions.

Instructions

Run a 9Router chat or vision model. Select the API dialect and supply its native request fields.

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": {
      "model": "<model>",
      "request": "<request>"
    },
    "name": "ninerouter_chat"
  }
}

Input Schema

NameRequiredDescriptionDefault
modelYes
streamNoCollect upstream SSE events into one bounded tool result.
dialectNoopenai
requestYesNative fields such as messages, input, or contents. Set model and stream separately.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare the safety profile (readOnlyHint=false, openWorldHint=true, idempotentHint=false, destructiveHint=false), so the description need not repeat it. What it does add is the pass-through contract: native request fields are forwarded to the selected dialect. It says nothing about cost, latency, upstream provider errors, or how the dialect affects behavior beyond field naming.

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?

Two short sentences with zero waste, and the core action is front-loaded before the parameter hint. The terseness edges toward under-specification rather than verbosity, but nothing is redundant.

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?

For a nested, free-form pass-through request object with no output schema and an arbitrary additionalProperties payload, the description is thin: it omits how to discover valid models, what the tool returns, and any dialect-specific caveats. An agent could call it, but only by guessing at several conventions.

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?

Schema coverage is 50% – model and dialect are undocumented in the schema – so the description must compensate. It usefully links dialect selection to the shape of request ("supply its native request fields"), which is real cross-parameter meaning, but it never explains what model expects or how the dialect values map to request shapes.

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 gives a specific verb+resource ("Run a 9Router chat or vision model") that clearly separates this tool from the modality-specific siblings such as generate_image, embed, or transcribe_audio. It stops short of naming any sibling explicitly, but the chat/vision scope is unambiguous.

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?

Usage is only implied by the phrase "chat or vision model" – an agent can infer this is the general text/vision completion path, but there is no explicit when-to-use statement, no exclusion of alternatives, and no pointer to ninerouter_list_models for obtaining a valid model value.

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