Skip to main content
Glama

Search activities

search_activities
Read-onlyIdempotent

Search guided outdoor activities bookable on opas.world across all listed guides. Filter by place, date, activity type, party size, language, and price. Returns estimated prices; call get_quote for an exact total.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "search_activities"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateNo
limitNo
queryNoFree text, like 'glacier hike'.
offsetNo
categoryNoActivity type code, like hiking or climbing.
currencyNoISO currency, like EUR.
languageNoLanguage the guide should speak, like en or fi.
latitudeNo
locationNoTown, region, or country.
longitudeNo
radius_kmNo
participantsNo
max_price_centsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, non-open-world), yet the description still adds real behavioral context: results are priced as estimates and require a follow-up get_quote call. It does not describe pagination behavior or what happens when no activities match, which are the remaining gaps for a 13-parameter search.

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?

Three short sentences, front-loaded with the primary capability, then the filter facets, then the pricing caveat and sibling hand-off. Nothing is repeated from the title and every clause carries information.

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?

For a 13-parameter tool with no output schema, the description does enough to convey the return shape (estimated prices) and the follow-up step, which is the most important missing piece. However, it is silent on the radius/coordinate search mode and on pagination defaults, both of which materially affect how an agent constructs calls.

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 only 38% across 13 parameters, so the description must compensate. The sentence "Filter by place, date, activity type, party size, language, and price" maps onto location, date, category, participants, language, and max_price_cents, but the geo trio (latitude/longitude/radius_km), the free-text query, currency, and the limit/offset pagination pair get no mention anywhere in prose.

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 ("Search guided outdoor activities bookable on opas.world") plus the scope "across all listed guides", which implicitly separates it from the guide-oriented sibling search_guides. It enumerates the filterable facets so an agent knows the kinds of queries supported, but never names a sibling outright, so differentiation is inferred 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?

"Returns estimated prices; call get_quote for an exact total" gives clear routing to the correct alternative for exact pricing, which is the most likely confusion point for an agent. There is no guidance on when not to use this tool (e.g. searching guides only vs. activities), so it stops short of full when/when-not coverage.

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