Skip to main content
Glama

LLM Model ID Check

Check an LLM model ID

check_model_id
Read-onlyIdempotent

Is this model ID current? Returns the model (release date, knowledge cutoff, context and output limits, price per million tokens) and newer models in the same family, or close suggestions if the ID is unknown.

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

Input Schema

NameRequiredDescriptionDefault
model_idYes

Output Schema

NameRequiredDescriptionDefault
existsYes

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 establish the read-only, closed-world, idempotent profile, so the description's added value is the disclosure of what comes back (release date, knowledge cutoff, context/output limits, per-million-token price) and, importantly, the fallback behavior of returning close suggestions when the ID is unknown. That unknown-ID behavior is genuine context not available in the annotations.

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 sentences, front-loaded with the core question and followed by the return payload and the failure path. Dense but readable; nothing is redundant, though the parenthetical field list is fairly heavy for the sentence that carries it.

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 an output schema present, the description need not enumerate return fields, and it still covers the main behavioral branch (unknown ID yields suggestions). What remains thin is parameter format guidance, which is the only meaningful omission for a one-param lookup tool.

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?

Only one parameter exists and schema coverage is 0%, so the schema contributes nothing beyond a 2-120 character string. The description frames it as 'this model ID' being checked, which conveys intent, but it gives no format hints (provider prefixes, version suffixes) that would help an agent construct a valid value.

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?

States a specific verb and resource: it verifies whether a given model ID is current and returns that model's metadata plus newer family members. The opening question 'Is this model ID current?' makes the lookup-by-ID nature clear and implicitly separates it from a listing tool like latest_models, though that sibling is never named.

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: an agent can infer this is for validating a known model ID before relying on it. There is no explicit guidance on when to prefer latest_models over this tool, nor any stated prerequisites or exclusions.

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