Skip to main content
Glama

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

entity_get

根据草料码取回该物的 ObjectCard v2:身份三元组(thing 物/code 码/binding 绑定)、属性、关系槽、状态(states=业务状态,code.status=码状态)、账本(records:总数+最近条目)、媒体、操作契约(actions 带注解与 humanUrl)。扫码或拿到码链接后的第一步。注意:thing.id 为过渡期码派生 id(idScheme=code-derived),勿持久化依赖;应持久化的稳定标识是 code.uri。缺席字段=未跟踪/不可解析,绝非 false 或空。带 formats 可附 markdown 等其它表示。

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

Input Schema

NameRequiredDescriptionDefault
codeYes草料码:扫码得到的 URL(如 https://qr71.cn/xxx/yyy)或 coding
formatsNo附加表示形式(默认仅结构化 json)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/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 disclosure burden, and it does add real behavioral context: absent fields mean untracked/unresolvable rather than false or empty, thing.id is a code-derived transitional id that must not be persisted, and code.uri is the stable identifier. That said, the description doesn't cover error/unresolvable-code behavior beyond a passing phrase, nor permission or rate-limit expectations, so the safety/operational profile is only partially disclosed.

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?

The content list is front-loaded and the operational caveats (id instability, stable identifier, absent-field meaning) follow in priority order with no filler. It is dense and presented as one run-on block rather than segmented, which slightly hurts scanability but doesn't waste sentences.

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 two-parameter read tool with no output schema, the description effectively supplies the return shape (identity triple, states vs code.status, records as total plus recent entries, media, actions with humanUrl). The id-stability warning and the absent-field convention are exactly the non-obvious facts an agent needs before calling and consuming the result.

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 documents both 'code' (URL or coding) and 'formats' (enum of json/markdown/jsonld/og, default json). The description's mention of code as a QR URL/coding and of attaching markdown-style representations largely restates the schema, adding no new syntax or edge-case semantics. Baseline 3 is appropriate.

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 ('根据草料码取回该物的 ObjectCard v2') and then enumerates exactly what the card contains (identity triple, attributes, relation slots, states, records, media, actions). This makes it distinguishable in practice from entity_records_list / entity_actions_list as an aggregate fetch, but it never names or contrasts those siblings explicitly, 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 Guidelines4/5

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

'扫码或拿到码链接后的第一步' gives a clear triggering context for when to reach for this tool. There is no explicit when-not guidance or named alternative for retrieving just one section (records, actions, bindings), which keeps it out of 5 territory.

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.