Skip to main content
Glama

Travel and pilgrimage reading

list_travel_articles
Read-onlyIdempotent

Recent pilgrimage and travel articles from the DharmikVibes blog shown on the site, with date, teaser and link.

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": "list_travel_articles"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior3/5

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

The annotations already establish that this is a safe, read-only, idempotent, non-destructive operation with no open-world access. The description adds useful context that the results come from the DharmikVibes blog and include date, teaser, and link, but it does not explain result limits, ordering, or freshness beyond the vague term "recent".

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?

The description is a single focused sentence that front-loads the resource and topic while efficiently noting the source and returned fields. It contains no filler or unnecessary repetition.

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 zero-parameter listing tool with annotations covering safety and no output schema, the description is nearly complete: it identifies the source and the returned fields. Minor gaps remain around how many articles are returned and how "recent" is defined, but the core behavior is clear.

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

Parameters4/5

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

The tool accepts no parameters, so there are no parameter semantics for the description to clarify and the baseline is 4. The schema coverage is complete, and the description appropriately avoids discussing nonexistent inputs.

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 states a specific resource (recent pilgrimage and travel articles from the DharmikVibes blog) and the fields returned (date, teaser, link), so an agent can understand what the tool provides. It does not explicitly distinguish this listing tool from siblings such as search or fetch, so it falls 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 Guidelines2/5

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

The description implies browsing recent blog articles but gives no explicit guidance on when to use this tool versus search, fetch, or other retrieval siblings. It also provides no when-not conditions or alternative recommendations.

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