Skip to main content
Glama

list_models

列出本站当前在架的大模型:模型标识、名称、类型、上下文长度、输入/输出单价。可按类型(text/image/audio/video)或关键词过滤。

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
limitNo最多返回多少条,默认 30
keywordNo按模型标识或显示名模糊匹配
app_typeNotext / image / audio / video,留空返回全部

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description must carry the behavioral burden. It does useful work by scoping results to models "当前在架" (currently available) and by enumerating the return fields, which compensates for the absent output schema, but it says nothing about permissions, rate limits, ordering, or whether pagination past the limit is possible.

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?

A single compact sentence, front-loaded with the verb and resource, followed by the return payload and the filter capability. The field enumeration is long but each item is informative; nothing is redundant padding.

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 three-parameter read-only list tool with no annotations and no output schema, the description covers what is returned and what can be filtered, which is close to what an agent needs before calling it. Only ordering and result-volume behavior remain unspecified.

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 100%, so the schema already defines limit, keyword, and app_type. The description reinforces the filter dimensions (type list, keyword matching) but adds no syntax or default behavior beyond what the schema states.

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?

"列出本站当前在架的大模型" names a specific verb (list) and resource (models), and the following clause enumerates exactly which fields come back (identifier, name, type, context length, input/output price). It is not confused with the sibling verbs compare_models or call_model, though the description never explicitly distinguishes itself from them.

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: filtering by type or keyword signals this is a discovery/browsing tool, but there is no explicit when-to-use clause, no when-not-to-use case, and no reference to compare_models or call_model as the next step after listing.

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.