Skip to main content
Glama

Apex Tatva — Botanical Provenance for AI Agents

Verify record seal

verify_record_seal
Read-onlyIdempotent

Check a SHA-256 seal you stored earlier against the current record. Tells you whether the record is unchanged since that hash was taken.

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>",
      "hash": "<hash>"
    },
    "name": "verify_record_seal"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesRecord id the hash belongs to.
hashYesThe 64-character SHA-256 seal hash you stored.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, closed-world behavior, so the safety profile is covered. The description adds genuine semantic context beyond them: it compares against the *current* record and produces a match/no-match answer tied to when the hash was captured. It does not say what happens if the record id is unknown, but that is a minor gap.

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 short sentences, front-loaded with the action and then the result. No filler, no restatement of the name.

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 two-parameter, read-only verification with no output schema, the description conveys what the agent gets back (a match verdict). Only the failure mode for an unknown record id is unaddressed, which is a small omission given the tool's simplicity.

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 coverage is 100% — both params document length, pattern, and meaning. The description only reinforces that the hash is a previously stored value bound to that record id, adding little beyond the schema. Baseline 3 is appropriate.

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?

Names a specific verb (verify/compare) and resource (SHA-256 seal vs. current record), and states the outcome — whether the record is unchanged since the hash was taken. It is clearly distinct from the search/list/get siblings, though it never names an alternative explicitly.

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 phrase 'a seal you stored earlier' implies the precondition (you must already hold a hash from a prior step), which is useful context. There is no explicit when-not guidance or mention of how this differs from a plain record fetch such as get_provenance_record.

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