get_chapterGet one chapter of the Bhagavad Gita (Vedic scripture) by number. Returns the Sanskrit name, transliteration, English meaning, summary, and verse count.
| Name | Required | Description | Default |
|---|---|---|---|
| chapter | Yes | Chapter number, 1-18. |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is clear. Description adds that it returns specific fields and uses chapter number, but doesn't disclose additional traits like pagination or error behavior. Consistent with annotations.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two sentences, no wasted words. First sentence states the action and resource, second lists return fields. Front-loaded and efficient.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
With one required parameter fully described in schema, comprehensive annotations, and no output schema needed (return fields listed in description), the description is complete for this simple tool.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Input schema has 100% coverage: the required 'chapter' property is described as 'Chapter number, 1-18.' Description reinforces 'by number' but adds no new semantic meaning beyond the schema. Baseline score of 3 applies.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Description uses specific verb 'Get' and resource 'chapter of the Bhagavad Gita', lists exact return fields (Sanskrit name, transliteration, English meaning, summary, verse count). Clearly distinguishes from sibling tools like get_verse and list_chapters by targeting a single chapter with number.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No explicit guidance on when to use this tool versus siblings. Usage is implied by the purpose ('get one chapter'), but no exclusion criteria or alternatives mentioned, which would help an agent decide between get_chapter, get_verse, and list_chapters.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Individual tools have detailed descriptions and mostly distinct purposes, but the mix of domains (scripture, finance, data lookup) could confuse an agent about which tool to choose for a given task. However, within each subdomain, tools are clearly differentiated.
Tool names follow no consistent pattern: some are verb_noun (ask_pipeworx, compare_entities), some are noun_verb (entity_profile, recent_changes), and some are single verbs (forget, recall). The mix of snake_case with varied starting parts makes naming unpredictable.
With 23 tools but only 3 related to the server's stated purpose (Bhagavad Gita), the tool count is severely mismatched. The vast majority belong to data analytics and finance, making the set feel bloated and mis-scoped.
For a Bhagavad Gita server, only list_chapters, get_chapter, and get_verse are provided, missing obvious features like search, commentary comparison, or multiple translations. The other tools are irrelevant to the domain, leaving it extremely incomplete.