OSM Edit MCP Server

Overview Schema Source Related Servers Discussions Admin

parse_natural_language_osm_request

Read-onlyIdempotent

Converts natural language requests into structured OpenStreetMap data, enabling map edits and queries from plain English commands.

Instructions

Parse a natural language request into structured OSM data.

Args: request: Natural language request for OSM operations

Returns: Dictionary containing parsed components of the request

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": {
      "request": "<request>"
    },
    "name": "parse_natural_language_osm_request"
  }
}

Input Schema

Name	Required	Description	Default
`request`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.1Sep 5, 2026

TDQS

A4/5.0

Behavior3/5

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

Annotations already cover readOnly, idempotent, openWorld, and non-destructive behavior, so the description does not need to repeat those. It adds that the tool returns a dictionary of parsed components, which is useful but minimal. No contradiction with annotations exists.

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?

The description is compact and well-structured, starting with a clear purpose sentence followed by concise Args and Returns sections. Every sentence adds value, and there is no redundant filler.

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?

For a simple one-parameter parser, the description covers purpose and parameter meaning, while the output schema handles return structure. However, it does not explain how the parsed output connects to other OSM tools or what types of natural language requests are supported, leaving slight ambiguity.

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 description coverage is 0%, so the description must compensate. The Args section defines 'request' as a natural language request for OSM operations, providing the essential meaning. It is helpful but lacks examples, language constraints, or scope details.

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's action: parsing a natural language request into structured OSM data. This distinguishes it from sibling tools that query, edit, or analyze OSM data directly. The verb 'Parse' and resource 'natural language request' are specific and unambiguous.

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 description implies usage when a natural language request needs to be converted into structured OSM data, but it gives no explicit guidance on when to prefer this tool over alternatives or how it fits into an OSM workflow. There are no exclusions or conditions provided.

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