Skip to main content
Glama

Edit an object

edit_object

Changes something placed: a label's text or a door's plate (text), a canvas's picture, a canvas's, label's or door's look, where a door leads (destination, arrive_at), whether a cannon is switched on (switched_on: false stops it firing, true starts it again once it has rested), or whom a zone is kept for (keep_for) and its name.

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": {
      "id": "<id>"
    },
    "name": "edit_object"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesIts id, as look gives it
lookNo
nameNoA few words to know the zone by in look
textNo
pictureNo
keep_forNoThe one person, by name, who may build in the zone besides you; "*" for you alone
arrive_atNo
destinationNo
switched_onNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false and destructiveHint=false, so the mutation/safety profile is known. The description adds real behavioral detail the annotations do not, notably that switched_on=false stops a cannon firing and true restarts it only 'once it has rested', but it omits what happens on permission/ownership failures or when a parameter does not apply to the target object type.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

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

It is a single dense sentence with no filler, but the structure is hard to parse, especially the run-on 'a canvas's, label's or door's look', and the one universally required argument (id) is never mentioned. Information is packed rather than front-loaded.

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?

For a nine-parameter mutation tool with 33% schema coverage and no output schema, the description covers most parameters and the key behavior of switched_on. It still leaves gaps on unsupported-field handling, error/permission behavior, and confirmation of what an edit returns.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With schema description coverage at 33%, the description carries the load well: it maps text to label text or a door's plate, picture to a canvas, look to canvas/label/door, destination and arrive_at to doors, switched_on to cannons, and keep_for/name to zones. This per-object-type applicability is meaningfully more than the schema provides, though `id` is left entirely to the schema and no format or validation hints are added.

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 mutation verb ('Changes') and enumerates the placed object types and properties it can alter (label text, door plate, canvas picture, look, door destination, cannon switch, zone keep_for/name). An agent can tell it edits existing placed objects, though it never distinguishes itself from siblings like change_appearance or appearance.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

There is no explicit when-to-use or when-not-to-use guidance and no alternative tool is named, even though siblings such as change_appearance and appearance plausibly overlap. The only implicit scoping comes from 'something placed', which tells the agent this is for existing objects, not creation.

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.