Skip to main content
Glama

Get model

get_model
Read-onlyIdempotent

Inspect a released model's input contract, units, assumptions and bounded scenario catalog. Supply scenario_id to also read that model's exact scenario defaults. This read starts no computation.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "limit": 20,
      "model_id": "returned-model_id"
    },
    "name": "get_model"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
offsetNo
model_idYes
scenario_idNo

Output Schema

NameRequiredDescriptionDefault
modelYes
relatedYes
warningsYes
context_completeYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds genuinely new behavioral context: this read starts no computation, and the scenario catalog is bounded. It says nothing about pagination behavior, result size, or what happens if a scenario_id or model_id does not resolve, which is the 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?

Two tight sentences with no filler, and the core purpose is front-loaded ahead of the optional scenario_id behavior. Minor cost: dense phrasing like 'bounded scenario catalog' is jargon the agent must decode, which slightly blunts the front-loading.

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?

An output schema exists and annotations cover the read-only profile, so return values need no explanation. However, for a four-parameter tool with zero schema description coverage, the definition omits pagination semantics and identifier expectations in both places, which is a real completeness gap for an otherwise well-scoped read tool.

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% across four parameters, so the description carries the full burden. It explains scenario_id's effect (returns that model's exact scenario defaults) and implies model_id selects the model, but limit and offset are never mentioned, leaving half the parameters with no documented meaning in either the schema or the description.

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 uses a specific verb ('Inspect') and resource ('a released model') and enumerates what is exposed: input contract, units, assumptions, and a bounded scenario catalog. It is clear on its own, but it never contrasts itself with nearby readers such as get_public_model or search_models, so sibling disambiguation is left to inference.

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?

It gives one conditional usage rule ('Supply scenario_id to also read that model's exact scenario defaults') and implies it is the non-computational inspection path with 'This read starts no computation', which points away from run_model_fit/run_model_scan/run_model_simulation without naming them. No explicit when-not or alternative-selection guidance is stated.

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