Skip to main content
Glama

Get model

get_model
Read-only

Parameters (with enums, ranges, defaults and whether they change the price), input slots for files, capabilities, credit pricing and an example request for one model.

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_id": "<model_id>"
    },
    "name": "get_model"
  }
}

Input Schema

NameRequiredDescriptionDefault
model_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

C2.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds some value by naming the categories of data returned (capabilities, credit pricing, example request), which hints at cost-planning use, but it discloses nothing about lookup failures, unknown model_id behavior, or freshness of pricing.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is short, but it opens with an ambiguous parenthetical listing that reads like response-field inventory rather than stating the operation up front. The sentence is not wasteful in length but is mis-front-loaded: purpose should precede contents.

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?

Because an output schema exists, return values need not be spelled out — yet the description spends its whole budget on return contents and omits the two things an agent actually needs: what the tool does and what model_id must be. For a single-required-parameter lookup tool this leaves a material gap.

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% and the sole parameter model_id is completely unaddressed by the description — no format, no source, no case/ID convention. The word "Parameters" in the description refers to the model's own inference parameters, not the tool's input, so it adds no meaning for model_id.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description never states a verb or the target resource; it enumerates what the response contains ("Parameters ... input slots for files, capabilities, credit pricing and an example request for one model"). An agent can infer this retrieves details for a single model, but the core action and its difference from the sibling list_models are left implicit.

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?

There is no when-to-use guidance, no statement of when to pick get_model over list_models, and no note that model_id presumably comes from list_models. The only hint is "for one model", which implies single-item retrieval but gives no routing advice.

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