Skip to main content
Glama

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

entity_actions_list

列出某草料码实体此刻可执行的操作清单(可填哪些表单、有哪些状态变更),仅列出、不执行。想知道'这个码能做什么'时用;拿到某个操作的完整填写字段用 entity_action_get,真正提交是写入工具(需授权)。

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

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/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 disclose the key trait: it is a read-only listing that never executes, and that real submission requires an authorized write tool. It does not describe the shape/freshness of the returned list (e.g., whether state is computed at call time), which keeps it from 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 the purpose and the non-execution caveat, then routing information; every clause carries information. Slightly dense with nested parentheses and semicolon-separated clauses, but not padded.

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 single-parameter read-only listing tool with no output schema and no annotations, the description covers purpose, scope, alternatives, and the read-only guarantee. The main remaining gap is what the list entries look like (identifier for each action to feed into entity_action_get), which an agent would still want.

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?

Only one parameter (code), and schema coverage is 100% with the schema already explaining that it accepts a scanned URL or coding. The description adds no format examples or matching rules beyond the schema, so the baseline 3 applies.

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 (列出/list) and resource (某草料码实体此刻可执行的操作清单), plus the scope of what is listed (fillable forms, status transitions) and that it only lists without executing. This clearly separates it from entity_action_get, which is named as the sibling that fetches full field details.

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 trigger ('想知道这个码能做什么时用'), names the alternative for a different need (entity_action_get for complete fill fields), and points out that actual submission happens in a separate write tool requiring authorization. Both when-to-use and when-to-use-something-else are covered.

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.