Skip to main content
Glama

Get activity details

get_activity
Read-onlyIdempotent

Get full details of one activity: description, guides, meeting point, equipment, requirements, deposit, and cancellation policy.

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_id": "<activity_id>"
    },
    "name": "get_activity"
  }
}

Input Schema

NameRequiredDescriptionDefault
localeNoLike en_US.
activity_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, closed-world, non-destructive behavior, so the safety profile is covered. The description adds real value by disclosing what the response actually contains (description, guides, meeting point, equipment, requirements, deposit, cancellation policy), which matters given there is no output schema. It stops short of noting auth requirements or behavior for an unknown/unpublished id.

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?

A single front-loaded sentence: verb, resource, then the enumerated payload. No filler, no restatement of the title, and every listed item is informative.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Adequate for a simple read tool with annotations covering safety and a description covering the return payload. However, it omits the locale parameter's semantics and says nothing about what happens when the activity_id is unknown or the activity is unpublished.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The description never mentions either parameter. activity_id is self-evident from its name and uuid format, but the locale parameter's effect (language of the returned content) is explained only by the terse schema note 'Like en_US.' With 50% schema coverage, the description does nothing to compensate for the 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?

States a specific verb and resource ('Get full details of one activity') and enumerates the returned content (guides, meeting point, deposit, cancellation policy). The phrase 'one activity' implicitly contrasts with the search_activities sibling, but no sibling is named, keeping it short of a 5.

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

Usage Guidelines3/5

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

Usage is only implied: an agent can infer it should call this when it already has an activity_id rather than a search query. There is no explicit when-to-use, when-not-to-use, or pointer to search_activities for discovery.

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