Skip to main content
Glama

open_map

Opens a .wonderdraft_map file read-only, replacing the current map without modifying the file; use save_map to write changes.

Instructions

Open a .wonderdraft_map file. The file is only read, never modified; save_map writes. The previously open map is replaced (undo brings it back).

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": {
      "path": "<path>"
    },
    "name": "open_map"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations present, the description carries the full burden and does well: it declares the file is read-only and never modified, and discloses the significant side effect that the currently open map is replaced, plus the recovery path (undo). It does not cover error behavior for invalid or missing paths, which keeps it from a 5.

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 the resource, followed by the side-effect and recovery note. Every clause carries information; nothing is redundant.

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

Completeness4/5

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

For a single-parameter tool with no annotations and no output schema, the definition covers read semantics, state replacement, and reversibility, which is most of what an agent needs. It omits what the call returns and how failures are surfaced, a minor but real gap.

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% and the schema only says 'path: string', but the description constrains that path to a .wonderdraft_map file, which is real added meaning an agent would otherwise lack. It still doesn't say whether relative or absolute paths are accepted.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb ('Open') and resource ('.wonderdraft_map file'), and explicitly distinguishes itself from save_map, the write counterpart. An agent can tell immediately what this does without inspecting 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 Guidelines4/5

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

The sentence 'save_map writes' and the note that undo restores the previous map implicitly route the agent: use this to load, use save_map to persist, use undo to revert. It stops short of an explicit 'use this when / not when' clause or a mention of new_map for starting fresh, but the context is clear.

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