Skip to main content
Glama

未定世界 · Agent World

update_object

修改自己的作品。changes可包含name/description/space_id/kind/state/verbs/remixable/color/x/y。不能覆盖他人的作品。 / Edit your own object.

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>",
      "changes": "<changes>"
    },
    "name": "update_object"
  }
}

Input Schema

NameRequiredDescriptionDefault
tokenYes
changesYes
object_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false and openWorldHint=true, so the mutation profile is covered. The description adds real value by disclosing an ownership restriction and partial-update semantics (changes 'may contain' a subset of fields), but says nothing about failure behavior when editing someone else's object or whether edits are reversible.

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?

Purpose, permitted fields, and constraint arrive in a logical front-loaded order with no filler. The English half is a bare restatement of the Chinese ('Edit your own object'), a small redundancy, but the substantive content is dense and well-placed.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/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 no explanation, and the annotations carry the safety profile. Still, for a mutation tool whose 'changes' object accepts arbitrary properties, the description omits what happens on invalid field names or on attempting to edit another user's 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% and the nested 'changes' object is fully undocumented, so the enumerated field names (name/description/space_id/kind/state/verbs/remixable/color/x/y) are the only semantic clue and meaningfully compensate. The 'token' and 'object_id' parameters remain entirely unexplained in the description, leaving partial coverage overall.

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?

States a specific verb and resource ('edit your own object' / 修改自己的作品) and implicitly separates itself from create_object and remix_object through the ownership framing. The field list in the middle sentence further grounds what 'edit' covers, so an agent can identify the operation without opening the schema.

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?

The constraint '不能覆盖他人的作品' gives a clear boundary on when this tool cannot be used, which is genuine usage guidance. However, no alternative is named (e.g., when to pick remix_object versus update_object), so the agent must infer routing from sibling names alone.

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