mappls-mcp

poi_along_route

Discover points of interest along a route by providing its encoded polyline. Useful for locating fuel, food, or ATMs on the way.

Instructions

Find points of interest along a route — useful for finding fuel stations, restaurants, or ATMs on the way from A to B. Requires the encoded polyline from get_directions.

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": {
      "path": "<path>",
      "category": "<category>"
    },
    "name": "poi_along_route"
  }
}

Input Schema

Name	Required	Description
`path`	Yes	Encoded polyline geometry string (from the 'geometry' field of get_directions response)
`buffer`	No	Search buffer in metres on each side of the route (default 300)
`category`	Yes	POI category code (e.g. 'FODCOF' for food & coffee, 'FINATM' for ATMs, 'PETPTM' for petrol pumps)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.0.1Jul 28, 2026

TDQS

A3.7/5.0

Behavior2/5

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

No annotations are provided, so the description must fully disclose behavioral traits. It only mentions the prerequisite dependency but does not explain error cases (e.g., invalid polyline, no results found), rate limits, authentication needs, or the ownership status of the operation. This is insufficient for a tool with no annotation coverage.

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 two sentences with no wasted words. It is front-loaded with the main purpose and immediately follows with a critical prerequisite. Ideal conciseness.

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 tool with three parameters, no output schema, and no annotations, the description covers the purpose and a key dependency but omits the return format, behavior when no POIs are found, and potential errors. It is adequate but not fully complete.

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 100%, so the baseline is 3. The description reinforces the dependency between 'path' and get_directions, which adds context, but does not significantly enhance the meaning beyond what the schema already provides for each parameter.

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 verb 'find', the resource 'points of interest along a route', and gives concrete examples (fuel stations, restaurants, ATMs). It distinguishes itself from sibling tools like nearby_search by focusing on route-based search.

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 provides clear usage context: finding amenities along a route. It explicitly states the prerequisite of needing the encoded polyline from get_directions. However, it does not mention when not to use this tool or name alternative tools for different scenarios.

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

Deploy Server