Skip to main content
Glama

China Source · 中国信源

List China Source directory

list
Read-only

中国信源列目录:列出某相对目录下的条目。只读。

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"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathNo相对目录, 缺省为根
limitNo条数, 默认 20

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true, and the description merely echoes that with '只读', adding no new safety context. It does not mention truncation/limit behavior, ordering of entries, or what happens for an invalid relative path, so it stays at the annotated baseline.

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 very short clauses, front-loaded with the resource and the constraint ('相对目录'). No filler, though the extreme brevity is arguably under-specification rather than elegance.

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?

For a two-parameter, parameterless-required read tool with full schema coverage and a readOnly annotation, the essentials are covered. With no output schema, though, the description could usefully say what an entry looks like or how listing is bounded, and it offers no orientation against its siblings.

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 both parameters are already documented. The description restates that the path is a relative directory ('相对目录'), reinforcing but not extending the schema; the limit parameter is untouched.

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 gives a specific verb+resource ('列出某相对目录下的条目') scoped to the China-source directory, so an agent knows it enumerates entries in a folder. However, it never distinguishes itself from the sibling tools 'find' and 'get', which a generic name like 'list' makes especially risky.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no statement of when to use this tool versus 'find' (search) or 'get' (fetch a single item). The only usage hint is the read-only marker, so the agent must infer that this is the enumeration tool.

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