Skip to main content
Glama

Spaghetti and Summits — First-Hand Dolomites Adventures

list_rifugios

Read-only

List first-hand English rifugio guides on Spaghetti and Summits. Returns each rifugio's name and the URL of the guide on the blog. Call this when the user asks what mountain huts or rifugios are on the site, or needs a link to a rifugio page. Provide a short reason explaining why you are calling this tool for the current task. Do not include personal or sensitive information in the reason.

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": {
      "reason": "<reason>"
    },
    "name": "list_rifugios"
  }
}

Input Schema

NameRequiredDescriptionDefault
reasonYesBriefly explain why this tool is needed for the current task. Do not include personal or sensitive information.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / $schema
      Added value: +"http://json-schema.org/draft-07/schema#"
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / reason
      Added value: +{
      +  "description": "Briefly explain why this tool is needed for the current task. Do not include personal or sensitive information.",
      +  "maxLength": 3000,
      +  "minLength": 1,
      +  "type": "string"
      +}
    • addedInput schema / required
      Added value: +[
      +  "reason"
      +]
  2. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description adds genuinely useful context beyond that: the result is limited to first-hand English guides and returns exactly two fields (name and blog guide URL). It does not say whether results are paginated or how many are returned.

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?

Purpose and trigger conditions are front-loaded in the first two sentences, with zero ambiguity. The trailing two sentences about including a short reason duplicate the schema field description and consume roughly a third of the text without adding value.

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?

For a single-parameter, read-only listing tool with no output schema, the description covers purpose, triggers, and return shape (name + URL), which is nearly everything an agent needs. The remaining gap is result-set behavior such as pagination or total counts.

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% and the single 'reason' parameter is fully documented in the schema, including the same privacy caution. The description restates that instruction rather than adding new meaning (e.g., expected length or examples). Baseline 3 applies since the schema does all the work.

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 opens with a specific verb+resource and scope: 'List first-hand English rifugio guides on Spaghetti and Summits,' and states what each result contains (name plus guide URL). It is clearly distinguishable from list_climbing_routes and list_ski_resorts by resource, though it never explicitly names or contrasts those siblings.

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?

It gives explicit trigger conditions: when the user asks what mountain huts/rifugios are on the site, or needs a link to a rifugio page. That is clear positive guidance, but there is no statement of when NOT to use it (e.g., for non-English guides or off-site huts).

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources