Skip to main content
Glama

Search guides

search_guides
Read-onlyIdempotent

Find guides listed on opas.world by name, activity, language, category, and verified credentials. Use this to compare guides before booking an activity.

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

Input Schema

NameRequiredDescriptionDefault
limitNo
queryNoFree text, like 'Chamonix'.
offsetNo
categoryNoActivity type code.
languageNoLanguage code, like en or fi.
latitudeNo
locationNoTown, region, or country.
longitudeNo
credentialNoCredential code, like ifmga or no-nortind.
verified_onlyNoOnly return guides with a verified credential.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered and the description only needs to add context. It adds the data source (opas.world) and the pre-booking comparison intent, but says nothing about result ordering, pagination behavior via limit/offset, or whether facets combine as AND filters.

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?

Two tight sentences with the capability front-loaded and the usage note second; nothing is padded or redundant. The facet enumeration slightly re-states the parameter list rather than adding new meaning, which is the only inefficiency.

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 10-parameter, fully optional search with no output schema, the description leaves the agent guessing on pagination semantics, geo-filter interaction between location and latitude/longitude, and what a result contains. It is adequate to call the tool correctly but not complete enough to call it optimally.

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 60%, so the baseline is 3. The description maps facets to several params (name→query, activity→category, language, credentials→credential/verified_only), but limit, offset, latitude, and longitude are undocumented in both the schema and the prose, and the description never explains that all filters are optional or how they combine.

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?

"Find guides listed on opas.world" states a specific verb and resource, and the facet list (name, activity, language, category, credentials) makes clear this is a multi-criteria guide lookup, distinguishable from search_activities. It never explicitly names a sibling or a single-guide retrieval alternative, so it stops short of 5.

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 this to compare guides before booking an activity" gives a clear situational trigger tied to the booking flow, which is the useful context an agent needs. It offers no exclusions or named alternatives (e.g., when to search activities instead of guides), which keeps it out of the 5 tier.

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