Skip to main content
Glama

Vedha360

Get a scripture story

get_story
Read-onlyIdempotent

One scripture story with its full retelling, cover-image credit and where the episode is in the Library.

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": {
      "story_id": "<story_id>"
    },
    "name": "get_story"
  }
}

Input Schema

NameRequiredDescriptionDefault
story_idYesStory id from list_stories

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

The annotations already declare readOnly, idempotent, non-destructive, closed-world behavior. The description adds meaningful payload scope: full retelling, cover-image credit, and Library episode location, which tells the agent what content to expect beyond the safety profile. It does not cover error behavior or permissions, but those are lower priority given the annotations and output schema.

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 compact sentence with no filler, and it front-loads the core resource ('One scripture story') before listing the included content. Every phrase adds useful information.

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 getter with annotations and an output schema, the description provides enough scope about what is returned and when the tool is relevant. It omits explicit routing from list_stories, but that workflow detail is covered in the schema's parameter description.

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%, so the story_id parameter is already fully documented, including that it comes from list_stories. The description adds no parameter-level meaning beyond indicating that one scripture story is returned, 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 identifies the resource precisely as 'One scripture story' and enumerates payload details ('full retelling, cover-image credit and where the episode is in the Library'), making it distinguishable from list-oriented siblings. It does not explicitly state a retrieval verb or name a sibling alternative, so it stops short of full sibling differentiation.

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 contains no explicit when-to-use or when-not-to-use guidance and does not name alternatives such as list_stories. The only workflow hint appears in the schema's story_id description ('Story id from list_stories'), not in the description itself.

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