Skip to main content
Glama
bedrock-map-builder-mcp

bedrock-map-builder-mcp

by xRookieFight

plan_edit

Modify a plan by appending steps, inserting steps after a specified step, or setting step statuses to rerun pending steps or skip steps.

Instructions

Change a plan: append steps, insert after a step, or set a step's status (pending to rerun, skipped to jump over it).

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": {
      "plan": "<plan>"
    },
    "name": "plan_edit"
  }
}

Input Schema

NameRequiredDescriptionDefault
addNo
planYes
afterNo
set_statusNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations are empty, so the description carries the full burden. It usefully explains the semantics of the status values ('pending to rerun, skipped to jump over it'), which is real behavioral insight, but it never says whether edits are allowed on a running plan, whether they persist, or what happens if the referenced step or plan does not exist.

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?

One front-loaded sentence with the resource first and the three modes enumerated; every clause carries information and nothing is padded.

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?

For a mutation tool with no annotations, no output schema, four parameters, and nested step objects, the description covers the operation modes but leaves the required plan argument, step structure, and side-effect/failure behavior undocumented.

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

Parameters3/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; it does map three of the four parameters to concrete operations (append→add, insert after→after, status→set_status). However it never explains the required 'plan' identifier, the shape of a step (tool/args/note), or the 'done' enum value that the schema allows.

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

Purpose4/5

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

The description gives a specific verb ('Change') and resource ('a plan') and enumerates the three supported mutations: append, insert after, set status. It implicitly separates itself from plan_create/plan_run/plan_show by framing the tool as modifying an existing plan, though it never names a sibling.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

The three modes are spelled out, so an agent can infer which operation to pick for a given intent, but there is no explicit when-to-use guidance, no prerequisite (e.g., plan must already exist), and no routing advice relative to plan_create or plan_run.

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