Skip to main content
Glama

Get one model

get_model
Read-only

One model by id (vendor/model, e.g. anthropic/claude-sonnet-4.5): every provider's offering with its price history, capabilities, limits and dates, and the model's quality scores. Counts as one call.

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

Input Schema

NameRequiredDescriptionDefault
atNoISO date or time: return the price revision in force then.
idYesThe model's id, `vendor/model`, or an alias of it.
providerNoOnly this provider's offering.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint=true, openWorldHint=false), so the description's contribution is the payload shape — all providers' offerings plus price history and quality scores — and the metering note 'Counts as one call,' which is a real cost signal an agent should weigh. It does not say what happens on an unknown id or alias (error vs. empty), which is the main remaining behavioral gap.

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 the resource and id format first, then the return payload, then the cost note — dense and waste-free. The mid-sentence list of returned fields is slightly run-on, but every clause carries information.

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

Completeness4/5

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

With no output schema, the description correctly shouldered the burden of describing return contents, and it does so thoroughly. Missing pieces relative to a lookup tool are minor: no behavior for unknown ids and no clarification of how the `at` date parameter interacts with the returned price history.

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 100%, so all three parameters are already documented, and the description largely restates the id format that the schema itself specifies, adding only a concrete example (`anthropic/claude-sonnet-4.5`). The `at` and `provider` parameters are not elaborated on in the description, so it does not meaningfully exceed the schema baseline.

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 states a specific verb and resource (retrieve one model by id) and enumerates the payload: every provider's offering with price history, capabilities, limits, dates, and quality scores. The phrase 'one model by id' implicitly contrasts with list_models, but it never names that sibling, so differentiation is left to inference rather than asserted.

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: the agent can infer this is the lookup for when it already knows a model id, as opposed to browsing. There is no explicit when-to-use, no when-not-to-use, and no mention of resolve (which appears to handle aliases per its name) as the alternative when an id is unknown.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources