Skip to main content
Glama
Sign In

Mappu

by ai.mappu
OverviewDiscussionsAdmin

Get the links to take a Mappu walk

mappu_get_walk_links
Read-onlyIdempotent

Get the links for taking a Mappu walk: for a published walk, or for the walks at a city or landmark. Use it when the traveler asks how to take a Mappu walk, whether it is free, or what it costs. Returns the free walk or audio-guide page on mappu.ai, which needs no account, and, where Mappu sells it on its own website, the page for a paid two-hour live walk with Mappu, which needs no account either. Says which part is free and which is paid. Nothing is charged in the chat: the paid page opens on mappu.ai, where the price shows before paying.

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_walk_links"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathNoExact public walk or guide path from a previous Mappu result, not a URL.
queryYesThe walk, city or landmark, not personal details.
localeNoen

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior5/5

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

Annotations already cover read-only, idempotent, non-destructive and closed-world, so the bar is low, yet the description adds real substance: it returns free walk or audio-guide pages requiring no account, plus a paid two-hour live-walk page where the price is shown before paying. It also pre-empts a likely agent concern by stating that nothing is charged in the chat. That is meaningful behavioral context not present in any structured field.

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?

The opening sentence front-loads both the action and the two modes, and the free-vs-paid distinction arrives before the cost details. It is slightly long and repeats the 'needs no account' clause twice, which is the only padding.

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?

With no output schema and a simple flat three-parameter input, the description carries the return-value burden well, describing both the free page and the optional paid page and how pricing is disclosed. The only omission is locale handling, which is minor for a link-retrieval tool.

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?

Schema coverage is 67%, and the description compensates by explaining the two lookup modes that correspond to path ('a published walk') and query ('the walks at a city or landmark'), which clarifies when each is appropriate. The locale parameter and its enum are unmentioned in both description and schema, leaving one gap.

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?

It states a specific verb and resource ('Get the links for taking a Mappu walk') and enumerates the two lookup modes: a published walk, or walks at a city or landmark. That maps cleanly onto the path-vs-query split. It stops short of naming sibling tools like mappu_find_walks, so the differentiation from discovery-style tools is implied rather than explicit.

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?

'Use it when the traveler asks how to take a Mappu walk, whether it is free, or what it costs' gives a concrete triggering intent set. There are no explicit exclusions or named alternatives, so an agent must infer that discovery queries belong to mappu_find_walks rather than this tool.

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

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