Skip to main content
Glama

Action chain integrity check

privi_pro_action_chain_verify
Read-only

Verify a supplied sequence of previous hashes and action payloads. PAID ONLY: 5 prepaid credits; production billing required.

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": {
      "entries": "<entries>",
      "initial_sha256": "<initial_sha256>"
    },
    "name": "privi_pro_action_chain_verify"
  }
}

Input Schema

NameRequiredDescriptionDefault
entriesYes
initial_sha256Yes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior3/5

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

The annotations already establish read-only and closed-world behavior, so the description does not need to restate safety. It adds valuable billing context (5 prepaid credits, production billing required), but it does not state what a successful or failed verification looks like or whether credits are consumed on failure.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two compact sentences with the operation front-loaded and the billing constraint clearly separated. There is no wasted wording, though the extreme brevity contributes to the missing parameter and outcome details.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a paid, two-parameter verification tool with no output schema and no schema descriptions, the definition is under-specified. It does not clarify the required 'initial_sha256' anchor or describe the verification result, leaving significant gaps for an agent attempting to call it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With schema coverage at 0%, the description must define both required parameters. It adds real meaning for 'entries' by explaining that each entry is a previous hash and action payload, but it leaves 'initial_sha256' entirely unexplained—an agent cannot tell whether this is a genesis hash, a trusted anchor, or something else.

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 uses a specific verb ('Verify') and a concrete resource ('a supplied sequence of previous hashes and action payloads'), which is clearly distinct from the append sibling. It does not explicitly name an alternative, but the operation's scope is understandable 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 Guidelines3/5

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

The implied usage context is clear: call this when you have a hash chain to check. The paid-only constraint ('5 prepaid credits; production billing required') acts as a usage prerequisite, but there are no explicit when-not-to-use conditions or named alternatives.

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.