Skip to main content
Glama

list_models

Retrieve available models and their IDs, supported Effort levels, and defaults at runtime—with provider filters and refresh options—so agents can choose valid, permitted models for a task.

Instructions

実行時に取得したモデル一覧(ID・対応Effort・既定Effortなど)を返す。モデル名はハードコードされていない

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
refreshNoキャッシュを無視して再取得
providerNo省略時は全プロバイダー
include_hiddenNo
include_disallowedNoユーザー未許可のモデルも含める(実行は不可)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose one genuine trait: the list is fetched at runtime and not hardcoded. It does not clarify read-only safety, caching/refresh behavior, error conditions, or return shape, which leaves meaningful gaps for an unannotated tool.

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 compact sentences with the core purpose front-loaded and no wasted wording. The phrasing is terse to the point of slight ambiguity but remains efficient.

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?

There is no output schema, so the description is the only source for return values, and it only sketches them with 'など'. For a four-parameter discovery tool with no annotations, it should say more about caching, refresh semantics, and what the returned entries contain.

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 75%, so most parameters are already documented in the schema, including the notable include_disallowed caveat. The description adds no parameter-specific meaning and leaves include_hidden unexplained, but the schema does most of the work.

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 a specific verb and resource ('モデル一覧…を返す') and briefly lists returned fields (ID, supported Effort, default Effort). It distinguishes the tool's domain from siblings like list_providers, though it does not explicitly name any sibling.

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 note that model names are not hardcoded implies the agent should call this to discover valid model IDs rather than assume them. However, there is no explicit when-to-use/when-not guidance and no reference to alternatives like list_providers.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.