Mappu

Get an audio guide

mappu_get_audio_guide

Read-onlyIdempotent

Look up a published Mappu audio guide to a landmark or place. Use it when the traveler asks about a landmark's story or whether it is worth a visit ("tell me about the Colosseum", "what is the Alhambra like"), or names one in their plan. Send query with the landmark's name; to pick the exact guide from an earlier Mappu result (an audio-guide result of mappu_search_public_travel or a stop of mappu_find_walks), also send its path, such as /audio-guides/italy/rome/colosseum. Returns the guide page link, city, listening minutes, available languages, its sections in order, the venue's official website where Mappu has checked it, the walks that include it and a short description. The audio plays in Mappu, not in the chat.

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": {
      "query": "<query>"
    },
    "name": "mappu_get_audio_guide"
  }
}

Input Schema

Name	Required	Description	Default
`path`	No	Exact public guide path from a previous Mappu result, not a URL.
`query`	Yes	Landmark or place name.
`locale`	No		en

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 8, 2026
- addedInput schema / required
```
Added value: +[
+  "query"
+]
```

Changed1 schema field changedOct 31, 2026

changedInput schema / properties / locale / enum

Previous value: -[
-  "en",
-  "it",
-  "es",
-  "fr",
-  "de",
-  "pt"
-]New value: +[
+  "en",
+  "it",
+  "es",
+  "fr",
+  "de",
+  "pt",
+  "ja",
+  "zh-tw"
+]

First observedOct 16, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already cover the read-only, idempotent, non-destructive, closed-world profile, and the description adds genuine context: what the response contains (link, city, listening minutes, languages, sections, walks) and that audio plays in Mappu rather than the chat. It stops short of noting any failure or not-found behavior, but that is a minor gap given 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.

Conciseness4/5

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

Front-loaded with purpose, then usage, then parameter mechanics, then return contents; no filler sentences. The return-value enumeration is long but earns its place because no output schema exists.

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 three simple parameters and no output schema, the description carries the return-shape burden well and explains the query/path relationship. Only the locale parameter and behavior when no guide matches are left unaddressed.

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?

At 67% schema coverage the description usefully explains the path parameter's provenance and format with a concrete example, and clarifies that query is the landmark name. The locale parameter's meaning — presumably the language of the returned guide — is never explained in either place.

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?

States a specific verb and resource — "Look up a published Mappu audio guide to a landmark or place" — and distinguishes the lookup from search by explaining that mappu_search_public_travel / mappu_find_walks produce the path this tool consumes.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicit when-to-use triggers are given with concrete traveler utterances ("tell me about the Colosseum"), plus the decision rule for query-only versus query+path when a prior Mappu result exists.

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

All Mappu tools Inspect

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

Need Help?