Skip to main content
Glama

Apex Tatva — Botanical Provenance for AI Agents

Get provenance record

get_provenance_record
Read-onlyIdempotent

Fetch one provenance record by its id (from search_provenance or list_records), with its four tiers and SHA-256 seal.

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_provenance_record"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesRecord id, e.g. 'ashw-kshira'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true, idempotentHint=true, and openWorldHint=false, so the safety profile is covered. The description adds what the record contains (four tiers and a SHA-256 seal), which is useful return-shape context, but says nothing about what happens when the id is missing or invalid.

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?

A single sentence that front-loads the verb and resource, then the id source, then the returned payload. Nothing is redundant.

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 one-parameter read tool with a fully documented schema and safety annotations, this is nearly complete — it even sketches the returned structure (four tiers, SHA-256 seal). Only failure behavior for an unknown id is left unstated.

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% and the parameter itself is documented with an example, so the baseline is 3. The description adds meaning by telling the agent where the id value originates, which is not encoded anywhere 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 names a specific verb (fetch) and resource (one provenance record), and it explicitly says it retrieves a single record by id — implicitly distinguishing it from the sibling search/list tools. It stops just short of an explicit 'use X instead when...' statement.

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?

It tells the agent where the required id comes from (search_provenance or list_records), which establishes the usage context. There are no explicit when-not conditions or error cases, so it is clear but not exhaustive.

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