Skip to main content
Glama

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

entity_bindings_list

查某草料码的换绑历史:这个码何时指向过哪个物(审计场景)。当前世代码与物 1:1(historyCount=1),恒返回单条 current 绑定;换绑功能上线后返回完整绑定事件序列。thingId 为过渡期码派生 id,勿持久化依赖。

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

Input Schema

NameRequiredDescriptionDefault
codeYes草料码:URL(如 https://qr71.cn/xxx/yyy)或 coding

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

No annotations are supplied, so the description carries the full burden and does substantial work: it discloses that historyCount is currently 1 and the tool 恒返回单条 current 绑定, that a future rebinding feature will return the full event sequence, and that thingId is a transient derived id that must not be persisted. Missing only explicit read-only/authorization framing to reach a 5.

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 purpose, then behavior, then a caution — tight and information-dense with no filler. Slightly hurt by the compressed phrasing around 当前世代码与物 1:1, which reads awkwardly and could be clearer.

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 one-parameter tool with no annotations and no output schema, the description covers the important ground: what it returns now (one current binding), what it will return later, and a caveat on thingId stability. Only the general shape of the returned binding record itself is left implicit.

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?

There is exactly one parameter and the schema already documents it at 100% coverage (URL or coding form with an example). The description adds no syntax or format detail beyond that; its extra meaning is about return values and the transient thingId, not the `code` input, so baseline 3 applies.

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 verb+resource in Chinese: query a QR code's rebinding (换绑) history — when the code pointed at which entity. That is far more precise than the tool name alone. It does not explicitly distinguish itself from siblings like entity_records_list or entity_action_get, so it stops short of a 5.

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?

It names the audit scenario (审计场景) as the intended use, which is a real usage signal, and it warns that the tool currently yields only a single current binding, implicitly telling the agent not to expect history today. However, it never says when to prefer a sibling tool or when this call is redundant, so guidance is implied rather than explicit.

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.