Skip to main content
Glama

草料二维码 · 扫码端 (CaoLiao QR Code Scan-side)

entity_records_list

取某草料码所指物的完整账本(记录履历:巡检、报修、保养等),按时间倒序,游标分页。entity_get 的 records.preview 只给最近几条;要看完整历史用这个,返回的 nextPageToken 传回 page_token 取下一页。每条记录带 snapshot(当时的码+物),时间为 ISO 8601 带时区。

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "code": "<code>"
    },
    "name": "entity_records_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
codeYes草料码:URL(如 https://qr71.cn/xxx/yyy)或 coding
sizeNo每页条数(默认 20,上限 50)
page_tokenNo上一页返回的 nextPageToken;首页留空

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does most of the work: it discloses reverse-chronological ordering, cursor-based pagination, how to chain nextPageToken into page_token, and that each record embeds a snapshot of the code/entity at that moment. It does not state read-only status or any auth/permission requirements, which is the only meaningful gap for a history-listing 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?

Dense but well ordered: purpose first, then the sibling distinction, then pagination mechanics, then record contents. Every clause carries information, though the contrast with entity_get is stated in two overlapping ways and could be tightened.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a three-parameter listing tool with no output schema and no annotations, the description supplies what an agent needs: what is returned (records with snapshot and timestamp), the time format (ISO 8601 with timezone), sort order, and how to paginate to completion.

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?

Schema coverage is 100%, so baseline would be 3, but the description adds meaning beyond the schema by explaining the nextPageToken-to-page_token round trip, which the schema only gestures at. The size parameter and the code URL/coding formats are left to the schema, which is reasonable.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('取某草料码所指物的完整账本'), enumerates the record types covered (巡检、报修、保养等), and scopes it to a single code. It also explicitly contrasts itself with the sibling entity_get, so an agent can distinguish the two tools without opening either schema.

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

Usage Guidelines5/5

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

Gives an explicit decision rule: entity_get's records.preview only returns recent entries, so use this tool when the full history is needed. The alternative and the condition that selects it are both named, leaving nothing to inference.

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.