Skip to main content
Glama

Edit Map

edit_map

Edit individual Map sections—destination, notes, fog, or out-of-scope—without rewriting the rest. Uses expected_revision to prevent overwriting concurrent changes.

Instructions

Read a Map's Destination and Notes, or edit one typed section — set Destination or Notes, add or graduate a fog patch, rule something out of scope — without rewriting the others. Decisions-so-far is generated from resolved Tickets and never accepted as input. Mutations pass expected_revision from a prior read so concurrent sessions cannot clobber each other.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
rootNoWorkspace directory. Defaults to the session workspace.
notesNoReplace the Notes section.
createNoStart a missing Effort and its Map. Only for Effort/Map that do not exist yet — not a flag to send on every call. Does not change revision rules for mutations on an existing Map; create with no section fields reads an existing Map like a plain read.
effortYesEffort slug whose Map to read or edit.
add_fogNoAppend a fog patch under Not yet specified.
rule_outNoAppend a hand-ruled item under Out of scope. Never touches Decisions-so-far.
destinationNoReplace the Destination section.
graduate_fogNoRemove a fog patch matched on its text. Fails when none match.
expected_revisionNoRevision from a prior edit_map read. Required when overwriting an existing Map; omitted when creating one.
Behavior5/5

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

Beyond the annotations (readOnlyHint=false, idempotentHint=false), the description discloses partial-update behavior ('without rewriting the others'), the impossibility of setting Decisions-so-far, and the optimistic concurrency mechanism using expected_revision. These are meaningful behavioral details not captured elsewhere.

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?

Three sentences, front-loaded with the primary purpose, then two critical behavioral constraints. Every sentence earns its place with no filler or redundancy.

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?

The description covers read/edit operations, partial updates, the auto-generated status of Decisions-so-far, and concurrency control. However, it omits the create capability (starting a missing Effort/Map), which is a notable use case, though the schema documents it. Overall, it is largely complete for a complex mutation tool.

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 input schema already has 100% description coverage for all nine parameters. The description adds semantic grouping by mapping operations to parameter families and clarifies the role of expected_revision, supplementing the schema without redundancy.

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?

The description clearly states the tool reads a Map's Destination and Notes, or edits one typed section (Destination, Notes, fog patches, out-of-scope items) without rewriting others. This specific verb+resource combination distinguishes it from sibling tools like update_ticket or get_board.

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 description explains when to use the tool: to read a Map or edit specific sections without touching others. It also provides important usage constraints—Decisions-so-far is never accepted as input, and mutations require expected_revision from a prior read. However, it does not explicitly name alternative tools for related operations.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/51ck/frontier-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server