Skip to main content
Glama

List models

list_models
Read-only

The models this tracker knows by name — 'model' (the id a search and set_issue_models read), 'name', 'vendor' and 'via' (openmath: offered through Open Math OS). A suggestion, not a fence: any other model name is accepted and kept as written. 'roles' are the parts the screen offers.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_models"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover read-only, non-destructive and closed-world, so the bar is lower; the description nonetheless adds genuinely non-obvious behavior: the list is 'a suggestion, not a fence' and arbitrary model names are accepted and kept verbatim. Since there is no output schema, the field breakdown ('model', 'name', 'vendor', 'via', 'roles') also usefully discloses the return shape.

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?

Compact and front-loaded, with each clause carrying distinct information (field meanings, leniency policy, roles). It drifts slightly into cryptic compression — heavy quoting and fragments like 'the parts the screen offers' read as notes rather than prose.

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?

For a zero-parameter, read-only tool with no output schema, the essential gaps to fill are what comes back and what constraints apply — both are addressed. Minor omissions: it never states the result is a collection (vs. an object), nor whether 'roles' is attached per model or globally.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Zero parameters, so the baseline is 4; there is nothing in the schema the description needs to disambiguate. The description spends its words on return-field semantics instead, which is the right allocation.

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 names the resource precisely ('the models this tracker knows by name') and enumerates the fields the tool exposes, which lets an agent tell it apart from set_issue_models/get_issue_models by linking 'model' to those tools. It lacks an explicit verb like 'list'/'return', phrasing the purpose as a noun clause, but the content is specific enough to be unambiguous.

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?

No explicit when-to-use or when-not-to-use statement. The parenthetical that 'model' is 'the id a search and set_issue_models read' implicitly points an agent here before calling set_issue_models, but the agent must infer that ordering and there is no guidance on alternatives 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