Skip to main content
Glama
Sign In

Mapillary

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Mapillary Images Near

mapillary_images_near
Read-onlyIdempotent

Street-level images near a lat/lon point. Returns image ids, coordinates, capture time, compass heading, and a 1024px thumbnail URL. Example: mapillary_images_near({ lat: 40.7580, lon: -73.9855, radius: 30, _apiKey: "MLY|..." })

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "lat": 40.758,
      "lon": -73.9855,
      "radius": 30,
      "_apiKey": "your-mapillary-api-key"
    },
    "name": "mapillary_images_near"
  }
}

Input Schema

NameRequiredDescriptionDefault
latYesLatitude of the center point, in degrees (-90 to 90), e.g. 40.7580
lonYesLongitude of the center point, in degrees (-180 to 180), e.g. -73.9855
limitNoMax number of images to return (default 10, max 25)
radiusNoSearch radius in meters around the point (default 50, max 50)
_apiKeyYesMapillary access token (free — create an app token at mapillary.com/dashboard/developers). Looks like "MLY|...".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, open-world, and non-destructive, so the safety profile is covered. The description earns credit by disclosing the exact return payload (ids, coordinates, capture time, compass heading, 1024px thumbnail URL), which is important given there is no output schema. It stops short of noting coverage gaps or rate limits.

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?

Two sentences, front-loaded with the resource and return shape. The inline example largely duplicates the schema's examples block, which is the only wasted space; otherwise it is tight.

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?

With no output schema, the description responsibly enumerates return fields, and the schema supplies parameter detail plus the required apiKey. What is missing is routing guidance relative to the two sibling Mapillary tools, which matters in a 40+ tool catalog.

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 all five parameters—including defaults, ranges, and the apiKey format—are already fully documented in the schema. The description adds no parameter semantics beyond repeating an example that duplicates the schema's own examples array, so baseline 3 applies.

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 first sentence states a concrete resource and scope: street-level images within a proximity of a lat/lon point. This implicitly distinguishes it from the sibling mapillary_image (single image), though it never names that sibling or mapillary_detections explicitly.

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?

Usage is only implied by the phrase 'near a lat/lon point' and the inline example call. There is no statement of when to prefer this over mapillary_image or mapillary_detections, and no exclusions or prerequisites beyond the apiKey note carried in the schema.

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

All Mapillary toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources