Skip to main content
Glama

ninerouter_list_models

Read-onlyIdempotent

List chat models, fallback combos, or capability-specific models to choose the right model for routing or generation tasks.

Instructions

List chat models, fallback combos, or models for a specific capability.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "ninerouter_list_models"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindNochat

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.8/5.0
Behavior2/5

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

Annotations already declare read-only, idempotent, open-world, non-destructive behavior, so nothing is contradicted, but the description adds no behavioral context beyond them: no indication of return shape (names vs full model records), whether the list is environment-scoped, or what a 'fallback combo' entry looks like.

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?

A single front-loaded sentence with no filler. Its brevity is appropriate, though the space saved comes at the cost of the parameter and usage detail noted elsewhere.

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

Completeness3/5

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

With one optional enum parameter and no output schema, this is a simple tool and the description covers the core purpose. Still missing are the default behavior, the meaning of the less obvious kind values, and any hint of what the returned list contains.

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 description coverage is 0%, so the description must carry parameter meaning. It mentions 'chat' and 'specific capability' but never ties them to the kind parameter, and gives no explanation of the tts, stt, embedding, image-to-text, web, or gemini values, which are not self-evident.

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 (List) and resource (models) and names the kinds of listings available (chat models, fallback combos, capability-specific models). It is distinguishable from siblings like ninerouter_model_info or ninerouter_chat, though the phrase 'fallback combos' does not map cleanly onto any value in the kind enum.

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?

No guidance on when to choose this over ninerouter_model_info, which is the nearest alternative for model-related questions. The default of 'chat' when no kind is supplied is never mentioned, so the agent cannot infer that omitting the parameter yields chat models.

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