RouterBase MCP

List RouterBase models

routerbase_list_models

List AI models from RouterBase with filters for task modality, provider, or search query.

Instructions

List RouterBase models, optionally filtered by modality, provider, or search query.

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": "routerbase_list_models"
  }
}

Input Schema

Name	Required	Description
`page`	No	1-indexed page number.
`task`	No	Filter by modality. Multiple values are ORed.
`search`	No	Full-text search query.
`api_key`	No	Optional RouterBase API key. Prefer ROUTERBASE_API_KEY.
`per_page`	No	Results per page.
`provider`	No	Filter by provider names such as OpenAI, Anthropic, Google, or xAI.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 7, 2026

TDQS

A3.5/5.0

Behavior2/5

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

No annotations are provided, and the description is minimal. It does not disclose behavioral traits such as pagination behavior, authentication needs (though api_key param exists), rate limits, or what the output contains. The description adds little beyond the obvious.

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 description is a single, front-loaded sentence with no wasted words. It captures the core action and variability efficiently.

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?

The description is adequate for a simple list tool, but given 6 parameters, no output schema, and no annotations, it could provide more context about output format, pagination details, or defaults. It is minimally complete.

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 description coverage is 100%, so parameters are well-documented in the schema. The description adds no new semantic meaning beyond reiterating that filters exist. Baseline 3 is appropriate.

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 'List RouterBase models' and specifies optional filters (modality, provider, search), distinguishing it from siblings like routerbase_get_model (single model) and routerbase_chat_completion (chat).

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 use for listing with optional filters but does not explicitly state when to use it over alternatives or provide any when-not-to-use guidance. Sibling tools exist, but no differentiation criteria are given.

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

Deploy Server