Skip to main content
Glama
Sign In

Opentripmap

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Opentripmap Autosuggest

opentripmap_autosuggest
Read-onlyIdempotent

Typeahead / partial-name search for POIs near a lat/lon point. Matches place names by prefix within a radius — good for "find places starting with X near here". Returns matching POIs with xid, name, kinds, distance, and coordinates. Example: opentripmap_autosuggest({ name: "louv", lat: 48.8566, lon: 2.3522, radius: 5000, _apiKey: "your-key" })

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": 48.8566,
      "lon": 2.3522,
      "name": "louv",
      "radius": 5000,
      "_apiKey": "your-opentripmap-api-key"
    },
    "name": "opentripmap_autosuggest"
  }
}

Input Schema

NameRequiredDescriptionDefault
latYesLatitude of the search center
lonYesLongitude of the search center
langNoTwo-letter language code (default "en")
nameYesPartial place name to match, e.g. "louv"
kindsNoOptional comma-separated category filter
limitNoMax results to return (default 50)
radiusYesSearch radius in meters, e.g. 5000
_apiKeyYesOpenTripMap API key

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already establish read-only, idempotent, and non-destructive behavior. The description adds meaningful behavioral detail beyond annotations: prefix matching, radius-constrained search, and a concrete list of returned fields (xid, name, kinds, distance, coordinates). 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is two concise sentences plus an immediately actionable example. Purpose is front-loaded, and every part earns its place with no filler or redundancy.

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

Completeness5/5

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

For a read-only autosuggest tool with fully documented parameters, safety annotations, and a clear example, the description is complete enough. It covers input behavior, the matching semantics, and the return payload despite the absence of an output schema.

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?

The input schema already describes all 8 parameters at 100% coverage, so the baseline is 3. The description's example reinforces required parameters like name, lat, lon, radius, and _apiKey, but it does not add substantial new meaning beyond what the schema provides.

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 names a specific verb and resource: typeahead/partial-name search for POIs near a lat/lon point, and specifies prefix matching, radius, and returned fields. It is unambiguous, though it does not explicitly contrast with sibling tools like opentripmap_places_radius or opentripmap_geoname.

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 phrase 'good for "find places starting with X near here"' gives a clear context for when to use the tool. It stops short of naming alternatives or saying when not to use it, so it does not fully meet the 'when/when-not/alternatives' bar.

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

All Opentripmap 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