Skip to main content
Glama

Fetch an itinerary page

fetch
Read-onlyIdempotent

The full public text of one page (yatra itinerary, retreat programme, inclusions, travel help for seniors, NRIs and families) or an article card, with its URL.

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": {
      "id": "<id>"
    },
    "name": "fetch"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesAn id from search or list_trips (e.g. "journeys/kashi-shiva-consciousness", "retreats/return-to-yourself", "experiences/antar-yatra", "blog/<slug>") or a wellness.dharmikvibes.com URL.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / id / description
      Previous value: -"An id from search or list_offerings (e.g. \"journeys/kashi-shiva-consciousness\", \"retreats/return-to-yourself\", \"blog/<slug>\") or a wellness.dharmikvibes.com URL."New value: +"An id from search or list_trips (e.g. \"journeys/kashi-shiva-consciousness\", \"retreats/return-to-yourself\", \"experiences/antar-yatra\", \"blog/<slug>\") or a wellness.dharmikvibes.com URL."
  2. First observed

TDQS

B3.2/5.0
Behavior3/5

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

The annotations already declare read-only, idempotent, non-destructive behavior and closed-world scope, so the bar is lower. The description adds that the content is public and that a URL is included, but it does not describe failure behavior, pagination, or the exact response shape beyond 'full public text' or 'article card'.

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?

The description is a single compact sentence that front-loads the main return value. The parenthetical enumerates several page types efficiently, though it is somewhat list-heavy.

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 simple one-parameter fetch tool with rich annotations and full schema coverage, the core behavior is adequately stated. However, with no output schema, the description could more clearly define the returned structure and how this differs from get_trip_details.

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 the id parameter is already fully documented with examples and accepted forms. The description reinforces the content domain but adds no syntax, format, or constraint meaning beyond what the schema provides.

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 title and description make clear that this fetches a single page's public text or article card and returns its URL. It names concrete page types (itinerary, retreat programme, inclusions, senior/NRI/family help), but it does not explicitly distinguish the resource from siblings such as get_trip_details.

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?

The description gives no explicit when-to-use guidance, prerequisites, or alternatives. It implies fetching a page by id, but does not say when to choose this over get_trip_details, search, or list_travel_articles.

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