Skip to main content
Glama
Sign In

Vedaword

by com.vedaword
OverviewDiscussionsAdmin

List the works in the library

list_works
Read-only

List the works with their sizes, shelf, author and available languages. Call it at the start of a conversation about scripture, or when you need work slugs for filtering. The list is short by default: no descriptions.

Narrow it with category (a shelf: itihasa, purana, upanishad, vedanta, samhita, shastra, kavya, shruti, smriti; shruti is the upanishad shelf, smriti the itihasa and purana shelves) or with author (an id from list_authors). Set include_descriptions for a paragraph on each work.

It also tells you what is not translated: several works exist only in Russian. Check languages before promising the user an English text.

Input Schema

NameRequiredDescriptionDefault
authorNoOnly the works credited to this author id (see list_authors).
categoryNoOnly the works on this shelf.
languageNoPreferred language of the translations returned. Not a filter: works that exist only in Russian are returned in Russian, and each result says which language it is actually in. Default: en.
include_descriptionsNoAdd a paragraph describing each work. Default false.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  2. Changed3 schema fields changed
    • addedInput schema / properties / author
      Added value: +{
+  "description": "Only the works credited to this author id (see list_authors).",
+  "minLength": 1,
+  "type": "string"
+}
    • addedInput schema / properties / category
      Added value: +{
+  "description": "Only the works on this shelf.",
+  "enum": [
+    "itihasa",
+    "purana",
+    "upanishad",
+    "vedanta",
+    "samhita",
+    "shastra",
+    "kavya",
+    "shruti",
+    "smriti"
+  ],
+  "type": "string"
+}
    • addedInput schema / properties / include_descriptions
      Added value: +{
+  "description": "Add a paragraph describing each work. Default false.",
+  "type": "boolean"
+}
  3. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations cover read-only safety, but the description adds behavior they don't: the default response is deliberately terse ('no descriptions'), descriptions are opt-in, and several works exist only in Russian. Flagging a partial-coverage data caveat the agent would otherwise over-promise on is exactly the kind of disclosure annotations can't carry.

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?

Three short paragraphs, front-loaded with what you get and when to call it, then narrowing options, then the caveat. The shruti/smriti parenthetical is dense but load-bearing; no sentence is pure padding, though the response-shape sentence overlaps slightly with what the schema implies.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema, but the description names the returned fields and the default truncation, so the agent knows what it will receive. With four optional params and clear general shape, nothing needed to call it correctly or interpret results is missing.

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?

Schema coverage is 100%, so baseline is 3; the description earns an extra point by explaining relationships the schema doesn't encode — that `shruti` is the upanishad shelf and `smriti` spans itihasa plus purana, and that `author` takes an id from list_authors. It does restate the language-is-not-a-filter behavior already stated in the schema, which keeps it from a 5.

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?

Specific verb + resource ('List the works') plus the exact payload (sizes, shelf, author, available languages). It also implicitly separates itself from verse-level siblings by mentioning 'work slugs for filtering', so an agent knows this is the catalog-level entry point.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

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

Gives concrete trigger conditions ('at the start of a conversation about scripture', 'when you need work slugs for filtering') and points to the sibling list_authors as the source of author ids. The closing caution to check `languages` before promising an English text is a real usage constraint, not filler.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Vedaword toolsInspect
Try in Browser
Context All Your Agents Can ShareAgents share what they learn, hand off work, and hold it when you switch models. Start with 5 GB free.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources