Skip to main content
Glama

LLM Model ID Check

Latest models of a provider

latest_models
Read-onlyIdempotent

Newest models of a provider, optionally filtered by a word such as 'sonnet', 'mini' or 'flash'.

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": {
      "provider": "<provider>"
    },
    "name": "latest_models"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
filterNo
providerYes

Output Schema

NameRequiredDescriptionDefault
modelsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint=false, so the safety profile is covered. The description adds that results are the 'newest' models and that filtering is by a word, but says nothing about ordering, default result count, or empty-result behavior.

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?

A single front-loaded sentence with no filler; the resource comes first and the optional modifier second. 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?

An output schema exists, so return values need not be described, and the tool is a simple three-parameter read. The only meaningful omission is the limit parameter's semantics and default, which is a minor but real gap for a 0%-coverage schema.

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 description coverage is 0%, so the description must carry the load; it does explain the filter parameter with real examples, which the bare 'string, maxLength 40' schema does not. However, the limit parameter is never mentioned (no default, no meaning) and provider is only implied by 'of a provider', leaving a real gap.

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 resource (newest models) scoped to a provider, which is concrete enough to act on. It does not differentiate itself from the sibling check_model_id, so an agent gets no explicit signal about which of the two to pick.

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 word 'optionally' plus concrete filter examples ('sonnet', 'mini', 'flash') implies how and when to narrow results. There is no guidance on when to use this versus check_model_id, and no mention of what happens when the filter matches nothing.

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