Skip to main content
Glama

remove_objects

Deletes map objects by ID from Wonderdraft files; re-list IDs after each deletion because later IDs shift and further edits need current IDs.

Instructions

Delete objects. All ids refer to the state before the call; later ids of the same kind shift down afterwards, so re-list before further edits.

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": {
      "ids": "<ids>"
    },
    "name": "remove_objects"
  }
}

Input Schema

NameRequiredDescriptionDefault
idsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior2/5

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

With no annotations, the description carries the full burden. It does disclose the non-obvious index-shifting behavior, which is valuable, but it says nothing about whether deletion is permanent, whether invalid/unknown ids cause an error or are silently skipped, whether mixed id kinds are allowed, or what the call returns.

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?

Two short sentences, front-loaded with the action and immediately followed by the constraint that governs correct use. Nothing is wasted and no sentence is filler.

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 single-parameter destructive tool with no annotations and no output schema, the definition covers the core action and the ordering caveat. It is still incomplete on irreversibility, failure behavior for stale or unknown ids, and result format — all material for a delete operation.

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?

Schema coverage is 0%, so the description must explain 'ids' itself, and it does: ids index the pre-call state and are positional rather than stable handles. That is meaningful semantics beyond 'array of strings', though the id format and whether ids may span different object kinds are only hinted at.

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?

The description opens with a specific verb and resource ('Delete objects'), which is unambiguous. It does not distinguish itself from any sibling (e.g., undo, update_object), but no sibling appears to offer deletion, so an agent can still identify the right tool.

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?

Sequencing guidance is present ('re-list before further edits'), which is real usage advice, but it is about what to do after the call rather than when to choose this tool over an alternative. No exclusions or prerequisites (e.g., irreversibility, permissions) are stated.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.