OSM Edit MCP Server

Overview Schema Source Related Servers Discussions Admin

create_track_selection

Read-onlyIdempotent

Selects a continuous subsection of an analyzed GPX track segment by coordinates, timestamps, or point indices, enabling targeted analysis without duplicating data.

Instructions

Select one continuous subsection of an analyzed GPX without copying 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": {
      "track_id": "<track_id>",
      "segment_id": "<segment_id>"
    },
    "name": "create_track_selection"
  }
}

Input Schema

Name	Required	Description	Default
`end_lat`	No
`end_lon`	No
`end_time`	No
`track_id`	Yes
`start_lat`	No
`start_lon`	No
`segment_id`	Yes
`start_time`	No
`end_point_index`	No
`start_point_index`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.1Sep 5, 2026

TDQS

C2.9/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds the behavioral nuance that the selection does not copy the GPX data and that it is a continuous subsection, which is useful context beyond the annotations. No contradiction exists.

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?

The description is a single concise sentence with no filler and the core action is front-loaded. However, for a tool with 10 parameters and no schema documentation, the brevity leaves important context unaddressed, so it is not a perfect structure for this complexity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description is not complete enough for correct invocation. It does not explain how to specify the continuous subsection (e.g., by coordinate pair, time range, or point indices), what relationship the selection has to later sibling tools, or what the output represents. While annotations and the output schema reduce some burden, the 10-parameter surface with 0% schema coverage demands more context.

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 carries the full burden for explaining the 10 parameters. It provides no information about how start_lat/start_lon, start_time, start_point_index, and their end_ counterparts relate to one another, which parameters are required, or how the selection determines the subsection. Parameter names are somewhat self-explanatory, but that is not sufficient compensation.

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 states a clear verb and resource: 'Select one continuous subsection of an analyzed GPX.' The qualifier 'without copying it' adds useful distinction. However, it does not explicitly differentiate the tool from sibling tools like match_track_selection or analyze_gpx_track.

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

Usage Guidelines2/5

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

The description gives no explicit guidance on when to use this tool versus alternatives, and it does not mention prerequisites or follow-up steps. The phrase 'of an analyzed GPX' only weakly implies that analysis must happen first, which is not enough for confident tool selection.

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