Skip to main content
Glama
Sign In
mappls-mcp

mappls-mcp

by AmanMakesStuff
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

snap_to_road

Snaps a series of GPS coordinates to the nearest road, correcting noisy GPS traces from devices.

Instructions

Snap a series of GPS coordinates to the nearest road. Useful for cleaning up raw GPS traces from a device.

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": {
      "points": "<points>"
    },
    "name": "snap_to_road"
  }
}

Input Schema

NameRequiredDescriptionDefault
pointsYesSemicolon-separated lat,lng GPS points to snap to roads. e.g. '28.55,77.13;28.56,77.14'

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.1

TDQS

A4.2/5.0
Behavior3/5

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

No annotations are provided, so the description carries full burden. It indicates the tool modifies points by snapping them to roads, but lacks details on limitations, error handling, or processing constraints.

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 sentences, no fluff. Every word serves a purpose: the verb, the resource, the use case.

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?

Given the tool has only one parameter and no output schema, the description adequately covers the purpose and usage. It could mention output format or error cases, but the simplicity limits the need.

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?

The sole parameter 'points' has full schema description coverage (100%). The description adds a concrete example of the format, which adds value beyond the schema alone.

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 uses a specific verb 'snap' and resource 'GPS coordinates to nearest road', clearly distinguishing it from sibling tools like geocode or directions. It also states the use case 'cleaning up raw GPS traces'.

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 gives clear context by stating it's 'useful for cleaning up raw GPS traces', which implies when to use. However, it does not explicitly mention when not to use or list alternative tools.

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

Deploy Server

Other Tools