Skip to main content
Glama
Sign In

Opentripmap

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Opentripmap Place Detail

opentripmap_place_detail
Read-onlyIdempotent

Get full details for a single place by its OpenTripMap xid (obtained from opentripmap_places_radius or opentripmap_autosuggest). Returns name, address, categories, Wikidata/Wikipedia links, description extract, image, and website. Example: opentripmap_place_detail({ xid: "N123456", _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": {
      "xid": "N123456",
      "_apiKey": "your-opentripmap-api-key"
    },
    "name": "opentripmap_place_detail"
  }
}

Input Schema

NameRequiredDescriptionDefault
xidYesOpenTripMap place id (xid), e.g. "N123456" or "W789"
langNoTwo-letter language code for text (default "en")
_apiKeyYesOpenTripMap API key

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds value by disclosing what the response contains (name, address, categories, Wikidata/Wikipedia links, description, image, website), which is useful since there is no output schema.

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 three sentences with no filler. The purpose is front-loaded, the returned fields are listed compactly, and the inline example makes the expected call shape immediately clear.

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 simple read-only detail lookup with 3 parameters and no output schema, the description is complete: it explains the workflow, the required identifier, the parameter example, and the expected return contents. Nothing essential for invoking the tool correctly is missing.

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 covers 100% of parameters, so the baseline is 3. The description adds only a brief example and clarifies that xid is obtained from sibling tools, but it does not materially explain parameter formats or constraints beyond what the schema already provides.

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 states a clear verb ('Get full details'), a specific resource ('a single place'), and the required identifier ('OpenTripMap xid'), which distinguishes it from the list/search sibling tools. Mentioning that the xid comes from opentripmap_places_radius or opentripmap_autosuggest further differentiates this detail-lookup tool from those list-returning tools.

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: use this tool when you already have an xid from either opentripmap_places_radius or opentripmap_autosuggest. It does not explicitly spell out when not to use it, but the source-tool reference makes the intended workflow obvious.

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