Skip to main content
Glama
OSM Edit MCP Server

OSM Edit MCP Server

by skywinder

review_poi_polygon_duplicates

Read-only

Review and resolve blocking polygon duplicate candidates with evidence-backed decisions, rechecking versions and parentage, then store a new preview revision.

Instructions

Resolve every blocking polygon candidate in a new digest-bound revision.

Same decisions and evidence requirements as review_node_create_duplicates. The explicitly replaced source node is reviewed as a conversion, never as a distinct object. Search, source version and parentage are rechecked. This stores a new preview only. After an explicit user request to publish it, call apply_osm_edit immediately; it performs the single final host approval.

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": {
      "proposal_id": "<proposal_id>",
      "proposal_digest": "<proposal_digest>",
      "decisions": "<decisions>"
    },
    "name": "review_poi_polygon_duplicates"
  }
}

Input Schema

NameRequiredDescriptionDefault
decisionsYes
proposal_idYes
proposal_digestYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.4.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already cover safety (readOnlyHint, destructiveHint=false, idempotency) and open-world behavior, so the description focuses on what those annotations cannot convey: that this writes a new digest-bound preview revision, rechecks search/source version/parentage, treats the replaced source node as a conversion rather than a distinct object, and defers all publication to apply_osm_edit. The only friction is that "stores a new preview" implies persisted state against readOnlyHint=true, but since a preview artifact is non-destructive and idempotentHint=false already signals changing state, this is clarification rather than contradiction.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Five short sentences, front-loaded with the action and scope, then constraints, then the follow-up handoff to apply_osm_edit. No filler; the wording is dense but each sentence adds a distinct rule or precondition.

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?

An output schema exists, so return values need no explanation, and the description covers the mutation boundary, the review semantics, and the next-step tool. Gaps remain around what makes a candidate "blocking" and how decisions map to candidates, but the operational path is complete enough to invoke correctly.

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

Parameters2/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 carry parameter meaning, and it only partially does. "digest-bound revision" hints at proposal_digest, "every blocking polygon candidate" implies decisions must cover all candidates, and "evidence requirements" gestures at the decisions records — but proposal_id, the per-decision fields, and the required exact-version matching are never explained.

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 opens with a specific verb and resource: "Resolve every blocking polygon candidate in a new digest-bound revision." It distinguishes itself from the sibling review_node_create_duplicates by scope (polygon candidates vs node creation) and states the resolution workflow, so an agent can identify the tool without opening 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?

It gives explicit sequencing: store the preview here, and after an explicit user request to publish, call apply_osm_edit immediately, which performs host approval. It also points to review_node_create_duplicates as the semantic template for decisions and evidence. There is no explicit when-not guidance, but the preconditions are clear.

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