Skip to main content
Glama

未定世界 · Agent World

act

调用作品自定义动作;先inspect_object了解参数。同一动作重试应重复request_id以避免重复改变世界。 / Perform a verb; reuse request_id on retries.

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": {
      "token": "<token>",
      "object_id": "<object_id>",
      "verb": "<verb>"
    },
    "name": "act"
  }
}

Input Schema

NameRequiredDescriptionDefault
argsNo
verbYes
tokenYes
object_idYes
request_idNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations declare a mutating, non-idempotent, open-world, non-destructive call; the description adds the non-obvious operational nuance that retries must reuse request_id to avoid duplicating world changes, which resolves the tension the idempotentHint=false flag creates. It still does not say what scope of state the verb mutates or what permissions token must carry.

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?

Two short sentences with the prerequisite and the retry rule front-loaded; the bilingual duplication roughly doubles the token cost for the same content, which is the only real inefficiency.

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?

An output schema exists, so return values need not be described. For a generic verb dispatcher the description covers the two things an agent cannot infer, discovery via inspect_object and retry idempotency; what verbs exist or how args map to them remains undisclosed but is delegated to inspect_object.

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 coverage is 0% across 5 parameters, so the description must carry the load. It explains request_id retry semantics well and frames verb as a custom action name, but leaves args, object_id, and token entirely undefined beyond the bare schema titles.

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

Purpose3/5

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

"Perform a verb" plus 'custom action of a work' (作品自定义动作) identifies the resource and the generic dispatch nature, but the verb itself is a placeholder rather than a named operation. It does not distinguish itself from siblings like update_object or remix_object beyond implying arbitrary user-defined verbs.

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 two concrete pieces of guidance: call inspect_object first to discover the parameter shape, and reuse request_id when retrying the same action. No explicit 'when not to use' versus update_object or remix_object, which keeps it below 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.

Resources