Skip to main content
Glama

TripFinder.ca

Read a travel guide

get_guide
Read-onlyIdempotent

The full text of one TripFinder guide in Markdown, with its sources, FAQ and the points a traveller should confirm before booking.

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": {
      "slug": "<slug>"
    },
    "name": "get_guide"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesA guide slug from list_guides.

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, non-destructive, and closed-world, so the safety profile is covered. The description adds genuine value beyond that by disclosing what the response contains: full Markdown text, cited sources, FAQ, and booking caveats. This matters because there is no output schema, so the description is the only signal of return shape.

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?

A single sentence, front-loaded with the core action and format, with the content list appended efficiently. Nothing is wasted, though it is dense enough that the guide sections are compressed into a comma list rather than structured as separate points.

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 one-parameter read tool whose annotations cover safety and idempotency, the description supplies the missing return-value picture. Remaining gaps are minor: no mention of document size, truncation, or what happens when a slug is stale, which would help an agent reading long guides.

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 slug parameter already documents its pattern, length bound, and provenance from list_guides. The description adds no extra meaning such as slug case sensitivity or failure behavior for an unknown slug, so the baseline of 3 applies.

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 names the specific resource (one TripFinder guide), the operation (full text read), and the output format (Markdown) along with its sections: sources, FAQ, and pre-booking points to confirm. An agent can tell this is a single-item read rather than a listing. It does not explicitly contrast with list_guides or get_trip, so sibling differentiation is implied only.

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

Usage Guidelines2/5

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

There is no when-to-use or when-not-to-use guidance in the description. The only routing hint, that the slug comes from list_guides, lives in the schema rather than the description. The agent must infer that this tool follows a listing call and is not a substitute for get_trip or search_trips.

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