Skip to main content
Glama

Vedha360

List scripture stories

list_stories
Read-onlyIdempotent

Short stories from the scriptures (Vedha360 retellings): title, one-line lead, deity, cover image and credit. Use get_story for the full text.

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

Input Schema

NameRequiredDescriptionDefault
deityNoe.g. Krishna, Shiva, Rama, Devi
limitNo
offsetNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered. The description adds the meaningful behavioral fact that results are summaries only, not full content. It says nothing about result volume, ordering, or how limit/offset paginate the catalog.

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?

Two sentences, both earning their place: the first defines the payload, the second routes to the sibling. Content scope is front-loaded and there is no filler.

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?

An output schema exists, so return values need not be spelled out, and annotations cover the safety profile. What is missing is guidance on the three filters and pagination, which matters for a listing tool with a default limit of 20 and a max of 100.

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

Parameters2/5

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

Schema description coverage is only 33%: only 'deity' has a description, while 'limit' and 'offset' carry no documentation in the schema. The description does not compensate at all — it mentions deity only as a returned field rather than as a filter, and never explains page size, defaults, or how to page through results.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names the specific resource (Vedha360 scripture retellings) and enumerates exactly what each item carries: title, one-line lead, deity, cover image and credit. It also explicitly separates this tool from get_story, which returns the full text, so an agent can choose between them without opening either schema.

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?

It gives a clear routing rule: use this for the short retellings, use get_story when the full text is needed. There is no explicit statement of when NOT to use it (e.g. versus search_scripture for keyword lookup), but the browse-vs-read distinction is unambiguous.

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