Skip to main content
Glama

list_objects

Lists map objects by kind—symbol, label, path, or territory—optionally filtered to a bounding box in map pixels, so you can inspect and locate elements in a Wonderdraft map.

Instructions

List objects of one kind, optionally inside bbox [x0, y0, x1, y1] (map pixels).

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": {
      "kind": "<kind>"
    },
    "name": "list_objects"
  }
}

Input Schema

NameRequiredDescriptionDefault
bboxNo
kindYes
limitNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations supplied, the description carries the full behavioral burden, and it only implies a read-only listing. It says nothing about the default limit of 200, whether results are truncated or paginated, ordering, or what the returned objects look like — all material for a list tool with a capped result set.

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?

A single front-loaded sentence with no filler; the scope constraint and the optional bbox come in a sensible order. It is efficient, though the terseness edges toward under-specification rather than pure concision.

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

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a three-parameter tool with no annotations and no output schema, the description should explain the result set and the limit behavior, and it does neither. An agent can form the call but cannot predict truncation or return shape from this text.

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 0%, so the description must compensate, and it does partially: it spells out the bbox ordering as [x0, y0, x1, y1] and its unit (map pixels), which the schema only calls an array of numbers. However, the limit parameter is never mentioned and "kind" is only restated as "one kind" rather than explained, so the compensation is incomplete.

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 gives a specific verb and resource ("List objects") plus a scope constraint ("of one kind"), which separates it from siblings like list_asset_sets and list_themes that enumerate different resource types. It stops short of naming any sibling or stating how it differs from map_summary-style enumeration, so it is clear but not fully differentiated.

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 guidance, no exclusions, and no mention of alternatives such as map_summary or the add_*/update_object tools. The only usage signal is the implicit one that this enumerates existing objects, leaving the agent to infer the rest.

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