Skip to main content
Glama

map_summary

Retrieve a concise summary of a Wonderdraft map, including dimensions, theme, object counts, land fraction, included packs, file path, and unsaved status.

Instructions

Size, theme, object counts, land fraction, included packs, file path and unsaved flag.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "map_summary"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.8/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, yet it never states that this is a read-only operation with no side effects. The mention of an "unsaved flag" hints it reflects live in-memory document state rather than a persisted file, but that implication is not spelled out and permission/auth behavior is unaddressed.

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 short fragment with no filler, which is efficient, but it lacks a verb and reads as a truncated field list. Brevity here costs clarity rather than earning it.

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?

There is no output schema, so the enumerated fields partially compensate by telling the agent roughly what comes back. However, it gives no indication of value formats (units for size, fraction ranges, pack structure) or what the unsaved flag means for follow-up actions.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate; the baseline of 4 applies. The field list it provides is arguably a stand-in for return-value documentation rather than parameter semantics.

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?

The description is a noun-phrase list of attributes ("size, theme, object counts, land fraction, included packs, file path and unsaved flag") rather than a verb+resource statement. It implies a read of current map metadata, but an agent must infer the action; it does at least distinguish the content from siblings like render_preview or list_objects by naming aggregate map-level facts.

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 and no mention of alternatives such as list_objects, list_themes, or export_image. The agent gets no signal about whether this is the cheap first call before deeper inspection or a substitute for listing entities.

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