Skip to main content
Glama

Activity details

get_activity
Read-onlyIdempotent

Details of one activity by activity_key: description, what is included, duration, cancellation, photos and the page url. The price for a day is given live on the page when a date is chosen. Always give the traveller the url of every item as a clickable link, unchanged: it is the only way to book or buy.

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": {
      "activity_key": "<activity_key>"
    },
    "name": "get_activity"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNoLanguage of the answer and of the links: es, en, de, fr, it, pt, tr or ru. Default es.
activity_keyYesactivity_key returned by search_activities.

Output Schema

NameRequiredDescriptionDefault
errorNo
photosNo
messageNo
summaryNo
activityNo
durationNo
includedNo
descriptionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • removedOutput schema / properties / next_dates
      Removed value: -{
      -  "items": {
      -    "additionalProperties": true,
      -    "properties": {},
      -    "type": "object"
      -  },
      -  "type": "array"
      -}
  2. 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 readOnly, idempotent, non-destructive, closed-world, so the safety profile is covered. The description adds genuinely non-obvious behavior: the daily price is NOT returned here but shown live on the page once a date is chosen, and the url is the sole booking channel and must be surfaced verbatim. It does not address invalid or stale activity_key behavior.

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?

Three sentences, front-loaded with what is returned, then the price caveat, then the link directive. Nothing is wasted, though the field enumeration partly duplicates what the output schema already exposes.

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?

An output schema exists, so return structure need not be explained, yet the description still flags the critical expectation gap (no price without a date) and the mandatory link handling. Only edge cases such as an invalid or expired activity_key are left unaddressed.

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 coverage is 100%, so both activity_key and lang are fully documented in the schema, including the lang enum values and default. The description adds only the link-immutability requirement tied to lang's phrasing about links, so the schema carries most of the weight.

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 ('Details of one activity by activity_key') and enumerates exactly what comes back: description, inclusions, duration, cancellation, photos, page url. The activity_key reference ties it to search_activities, so an agent can tell it apart from the search 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?

Gives a clear use condition (retrieve details for a key returned by search_activities) and a strong operational directive: always pass the url to the traveller unchanged as a clickable link because it is the only booking path. It does not explicitly say when not to use it or name an alternative for browsing, but the usage context is unambiguous.

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.