Skip to main content
Glama

save_map

Saves the open Wonderdraft map to its original file or a given path; new maps require a path, and existing files get a timestamped .bak backup before overwrite.

Instructions

Save the open map. Without a path, overwrite the file it was opened from. New maps need a path. Before an existing file is overwritten a timestamped .bak copy is made, at most once per file per session and never of a file this server wrote itself. Returns the absolute path and the backup (or null).

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": "save_map"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.8/5.0
Behavior5/5

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

With zero annotations, the description carries the full burden and does so: it discloses the overwrite semantics, the timestamped .bak side effect, the once-per-file-per-session throttle, the exception for server-written files, and the return value. These are non-obvious behaviors an agent could not infer from the schema.

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?

Four short sentences, front-loaded with the action, then conditions, then side effects, then return value. Each sentence adds distinct information; no restatement of the name or filler.

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

Completeness5/5

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

There is no output schema, and the description supplies the return shape (absolute path plus backup or null). With no annotations and one parameter, the definition covers action, conditions, side effects, and results — enough to invoke correctly without further reading.

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

Parameters5/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 — the single path parameter's optionality, default behavior (overwrite the opened file), and required use case (new maps) are all explained. Nothing about the parameter is left to guesswork.

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 and resource ("Save the open map") as the first sentence, and the remainder scopes exactly which map instance is affected. No sibling tool performs saving, so this is unambiguous against the map_*/add_* family.

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?

Gives clear conditional guidance: omit path to overwrite the source file, supply a path for new maps. It does not name alternatives or explicitly say when not to save (e.g., before export_image or render_preview), but with no competing save tool the context is sufficient.

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