ModelRadar MCP

modelradar_get

Retrieve full details for a specific language model by ID, name, or OpenRouter ID. Use it to inspect model capabilities before routing tasks.

Instructions

Get full details for one model by id, name, or OpenRouter id.

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_or_name": "<id_or_name>"
    },
    "name": "modelradar_get"
  }
}

Input Schema

Name	Required	Description	Default
`id_or_name`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 6, 2026

TDQS

A3.7/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It mentions identifier types but does not disclose authentication requirements, rate limits, error behavior, or what 'full details' encompasses. The read-only nature is implied by 'Get' but not stated explicitly.

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 that states the operation and the key parameter semantics without any redundant words. It earns its place fully.

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?

For a one-parameter tool with no output schema and no annotations, the description explains the purpose and parameter meaning but omits return format and usage context. It is minimally viable but has clear gaps for an agent to fully understand what to expect.

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

Parameters4/5

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

The schema only defines id_or_name as a string with no description. The tool description compensates by specifying that the parameter can be an id, name, or OpenRouter id, adding crucial meaning that the schema alone does not provide.

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 uses a specific verb ('Get') and clearly identifies the resource ('full details for one model') and the accepted identifier types (id, name, OpenRouter id). This distinguishes it from sibling tools like search or latest, which imply broader or different operations.

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 usage when the user has a specific model identifier but does not explicitly state when to use this tool versus alternatives. There are no exclusions or comparisons with sibling tools, though the singular 'one model' hints its scoped purpose.

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

Deploy Server