Skip to main content
Glama

Apex Tatva — Botanical Provenance for AI Agents

Get a canonical source text

get_canon_text
Read-onlyIdempotent

Fetch one canonical source text by id (from search_canon). Returns its full record: title and native title, author, era, tradition or pillar, language, chapter and verse counts, synopsis, defining quoted line, and topic domains.

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": {
      "id": "<id>"
    },
    "name": "get_canon_text"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesCanon text id, e.g. 'charaka' or 'gyuzhi'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent and closed-world behavior, so the safety profile is covered. The description adds real value by enumerating the returned record's fields, which matters because no output schema exists; it does not mention error behavior for invalid ids.

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?

Two clauses: the lookup action with its id source is front-loaded, then the return payload. The field list is dense but each item earns its place given the absence of an output schema.

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?

A one-parameter read tool with full schema coverage, complete annotations and no output schema. The description supplies what is otherwise missing: the shape of the returned record.

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 'id' parameter is already documented with an example, making 3 the baseline. The description adds the provenance of that id (it comes from search_canon), which is meaningful routing context beyond the schema text.

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?

States a specific verb and resource ('Fetch one canonical source text by id') and contrasts it with the sibling search_canon, which produces the ids. An agent can distinguish a single-record lookup from a search without opening the schema.

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 parenthetical '(from search_canon)' tells the agent where ids come from, implying the intended lookup-after-search workflow. It does not state exclusions or what to do if the id is unknown, so it stops short of explicit when-not guidance.

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