Skip to main content
Glama

Edit Map

edit_map

Modify one Map section at a time—destination, notes, fog, or out-of-scope—without rewriting the others. Pass expected_revision from a prior read to ensure concurrent sessions do not clobber 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 the Effort and its Map if neither exists. Otherwise an unknown slug fails.
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?

Annotations already indicate a non-read-only, non-idempotent mutation. The description adds rich behavioral context: partial updates preserve other sections, Decisions-so-far is auto-generated from resolved Tickets, and optimistic concurrency via expected_revision prevents clobbering. This goes well beyond annotation hints.

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 dense, information-packed sentences with zero fluff. The first sentence front-loads the core action and scope, while the second adds critical constraints. Every clause earns its place.

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?

Despite having 9 parameters and no output schema, the description covers essential behaviors: read vs. edit modes, the single-section constraint, auto-generation of Decisions-so-far, and concurrency protection. Individual parameter details are fully covered by the schema, so the description is appropriately complete.

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 100%, so the baseline is 3. The description adds meaningful context by grouping parameters into coherent operations (set Destination/Notes, add/graduate fog, rule out) and explaining the purpose of expected_revision for concurrency. This adds value beyond what the schema already provides.

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 identifies the Map as the target resource and specifies the exact operations available: read/edit Destination and Notes, add/graduate fog patches, and rule items out of scope. It distinguishes from siblings by focusing on Map-specific actions and mentioning that other sections are preserved.

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 explicitly states the tool's scope (read/edit Map sections) and includes constraints such as 'one typed section' and 'never accepted as input' for Decisions-so-far. It does not name alternatives, but the differentiation from sibling tools (e.g., update_ticket) is implicit via the resource focus.

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