Skip to main content
Glama

List models

list_models
Read-onlyIdempotent

Every model you can put in a poll's panel right now: its provider and id (what create_poll's panel takes), name, lab, the search depths it is offered at, a typical answer's charge, and its last 30 days of cut-off and error rates. A model is offered only after it has been measured. (GET /api/v1/models)

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. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world behavior, yet the description still adds real context: models are offered only after being measured, and each record carries a typical answer charge plus 30 days of cut-off and error rates. It stops short of stating ordering, pagination, or cost of calling.

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?

Front-loaded with the resource and scope, followed by the returned fields and one caveat sentence. The field list is dense but every clause maps to a returned attribute; only the trailing '(GET /api/v1/models)' adds little for an agent.

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 no output schema and no parameters, the description carries the return-value burden and does so by naming each field, plus the availability rule that unmeasured models are excluded. Ordering/pagination are unaddressed, which is the main remaining gap for a list endpoint.

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?

The tool takes zero parameters, so the baseline is 4 and the description does not need to explain inputs. It usefully clarifies that the 'id' field in the response is the input create_poll's panel expects, which bridges output to another tool's parameter.

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 states a specific resource (the models available for a poll's panel) and enumerates the returned attributes, so an agent knows exactly what it gets. It implicitly distinguishes itself from siblings by naming create_poll's panel as the consumer, though it never says the verb 'list' or explicitly contrasts with other list_* tools.

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 implied rather than stated: the parenthetical 'what create_poll's panel takes' tells the agent this is the lookup step before create_poll. There is no explicit when-to-use/when-not framing and no named alternative, so guidance is inferable but not spelled out.

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.