Skip to main content
Glama

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

entity_action_get

取某个操作的完整可填字段 schema(字段名、类型、是否必填、可选项)。entity_actions_list 只列操作、不带字段;准备填某个表单前用这个拿到它的完整字段定义。读 schema 无需授权,提交才需要。

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

Input Schema

NameRequiredDescriptionDefault
codeYes草料码:URL(如 https://qr71.cn/xxx/yyy)或 coding
actionNo操作标识,形如 "record:1556557"(来自 entity_actions_list 的 action 字段)
tpl_idNo或直接给表单模板 id(与 action 二选一)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/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 real work: it discloses that reading the schema requires no authorization while submission does, which is exactly the kind of prerequisite an agent needs. It also implies read-only behavior by describing a schema fetch. It does not cover failure modes for an invalid code/action, 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short clauses: what it returns, what the sibling lacks, and when to call it, followed by the auth caveat. Every sentence earns its place and the return-content description is front-loaded.

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?

There is no output schema, so the description compensates by describing the shape of the returned field definitions, and it covers the auth distinction. For a simple read-only schema lookup this is nearly complete; only error/edge behavior (invalid code, unknown action) is unaddressed.

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 baseline is 3. The description adds no parameter-level detail beyond what is already in the schema — the action-vs-tpl_id alternative is spelled out in the schema itself ('与 action 二选一'), and the description only alludes to it indirectly.

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 ('取某个操作的完整可填字段 schema') and enumerates what the payload contains (field name, type, required flag, options). It also explicitly contrasts with entity_actions_list ('只列操作、不带字段'), so the agent can distinguish the two 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 Guidelines4/5

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

Gives a concrete triggering condition: use this before filling out a form, to obtain its full field definition. It also names the sibling tool that is not appropriate for this need. Lacks an explicit 'do not use when' clause (e.g., for reading submitted record values, where entity_records_list would apply), so it falls just short of a 5.

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.