Skip to main content
Glama
Sign In

Dhamma.Gift — Pāli Canon

by gift.dhamma
OverviewDiscussionsAdmin

get_text

Fetch a sutta by id (e.g. "dn22", "mn1", "sn56.11") — the Pali text (Mahāsaṅgīti) of every segment. Pali only by default; pass langs for translations, translators to name a translator (e.g. ["en_sujato"]), editions for the whole text of other Pali editions line by line (DN, MN, SN, AN). Same data as dhamma.gift/api/text.

Input Schema

NameRequiredDescriptionDefault
langsNoTranslation languages to include, e.g. ["ru","en"]. Default: none (Pali only).
suttaIdYesSutta id, e.g. dn22, mn1, sn56.11.
editionsNoOther Pali editions to add, each segment beside the Mahāsaṅgīti: bjt (Buddha Jayanti, Sri Lanka), my (Chaṭṭha Saṅgāyana, Myanmar), th (Siam Rath, Thailand), mso (Mahāsaṅgīti as printed, 2005), pts (Pali Text Society), or ["all"]. DN, MN, SN and AN only.
translatorsNoExplicit translator keys, e.g. ["en_sujato"] to include Sujato.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / editions
      Added value: +{
+  "description": "Other Pali editions to add, each segment beside the Mahāsaṅgīti: bjt (Buddha Jayanti, Sri Lanka), my (Chaṭṭha Saṅgāyana, Myanmar), th (Siam Rath, Thailand), mso (Mahāsaṅgīti as printed, 2005), pts (Pali Text Society), or [\"all\"]. DN, MN, SN and AN only.",
+  "items": {
+    "enum": [
+      "bjt",
+      "my",
+      "th",
+      "mso",
+      "pts",
+      "all"
+    ],
+    "type": "string"
+  },
+  "type": "array"
+}
  2. Changed1 schema field changed
    • changedInput schema / properties / suttaId / description
      Previous value: -"SuttaCentral-style id, e.g. dn22, mn1, sn56.11."New value: +"Sutta id, e.g. dn22, mn1, sn56.11."
  3. First observed

TDQS

A3.9/5.0
Behavior4/5

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

No annotations are provided, so the description carries the behavioral burden. It does well by stating the default is Pali only, that passages can include translations or other editions, and that editions are limited to DN, MN, SN, and AN. It still leaves minor gaps around error behavior and response structure.

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, front-loaded paragraph that starts with the core action and then summarizes defaults and optional behavior. It is dense but has little wasted text.

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 read tool with no annotations and no output schema, the description provides enough context to invoke it correctly: required suttaId, default Pali-only behavior, and optional translations and editions. It could say more about response shape or invalid-id handling, but the core invocation context is complete.

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 the schema already documents all four parameters. The description adds useful framing about defaults and how langs, translators, and editions affect the result, though most parameter details are already present in the schema.

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 verb and resource: fetch a sutta by id. It explains that the result is the Mahāsaṅgīti Pali text of every segment, which is clear. It does not explicitly differentiate itself from siblings such as compare_editions or compare_translations, 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 Guidelines3/5

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

The description implies usage by saying to pass langs for translations, translators to name a translator, and editions for other Pali editions. However, it does not explicitly say when to use this tool versus compare_editions, compare_translations, list_structure, or search.

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

All Dhamma.Gift — Pāli Canon toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources