Skip to main content
Glama

fojin — Buddhist Canon Tools

commentaries

What the historical commentators said about a passage of Buddhist scripture.

Give a line of a sūtra and get back the classical commentaries that gloss
it — each with the commentator's own words, the work it comes from, a
quality tier, and a resolvable citation. This is the layer no other tool
exposes for the Chinese canon: CBETA marks up almost none of it, and the
alignment behind this was derived text by text.

Two things to read carefully rather than skim. `total` is how many
commentators the passage actually has — `truncated` says the list you got
is a sample. And coverage is partial: roughly half of what a commentator
wrote is not aligned, so an absent commentator means "not in the data",
never "he said nothing". When nothing matches, `available_sutras` tells
you which sūtras have data at all — do not read a miss as silence from the
tradition.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNo
quoteYes

TDQS

A4.5/5.0
Behavior5/5

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

With no annotations, the description fully discloses behavioral traits: it explains the meaning of 'total' and 'truncated', the partial coverage of the data, and the significance of absent commentators. It also details the return contents (commentator's words, work, tier, citation), making behavior predictable.

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 well-structured with a clear opening statement, usage instruction, and important caveats. Every sentence adds value, and it is not unnecessarily verbose for the amount of critical detail it conveys.

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?

Despite having no output schema and no annotations, the description adequately covers input semantics, output structure, and interpretation caveats. It even explains how to interpret non-matches, making it sufficiently complete for a tool with two parameters.

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 0%, and the description clarifies the 'quote' parameter as a line of a sūtra, but it does not explain the 'limit' parameter beyond the schema's default. The output discussion of 'truncated' hints at limit's effect, but the parameter is not explicitly described.

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 clearly states that the tool returns historical commentaries for a given line of Buddhist scripture, with a specific verb ('get back') and resource ('classical commentaries'). It explicitly distinguishes this tool as the only one exposing this layer of the Chinese canon, setting it apart from siblings.

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?

The description provides clear usage context: give a line of a sūtra to get commentaries. It also gives guidance on interpreting no matches via available_sutras and warns against reading absences as authorial silence. However, it does not explicitly name alternative tools for other needs, though it implies uniqueness.

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.

TDQS

A4/5.0
Disambiguation5/5

Each tool targets a distinct resource or operation: commentaries for historical glosses, get_parallels for cross-tradition alignments, lookup_dictionary for terms, lookup_entity for entities, read_passage for full text, resolve_urn for citation resolution, search_corpus for semantic search, and verify_quote for verbatim verification. There is no overlap in purpose, and the boundaries are clear even between similar-looking lookups.

Naming Consistency4/5

Most tool names follow a consistent verb_noun snake_case pattern (get_parallels, lookup_dictionary, read_passage, resolve_urn, search_corpus, verify_quote). The lone exception is 'commentaries,' which is a noun rather than a verb_noun construction, but this is a minor deviation in an otherwise uniform set.

Tool Count5/5

With 8 tools, this server is well-scoped for a specialized Buddhist canon research domain. Each tool earns its place, covering search, retrieval, verification, lookup, and cross-reference without redundancy or bloat.

Completeness5/5

The toolset covers the complete research workflow: finding passages (search_corpus), reading them (read_passage), verifying quotes (verify_quote), resolving citations (resolve_urn), understanding terms (lookup_dictionary) and entities (lookup_entity), and exploring cross-tradition parallels (get_parallels) and commentaries (commentaries). No significant gaps exist for the stated purpose.