Skip to main content
Glama

SCRIPTMASTERLABS — Verdict Protocol

Check capsule hash integrity

verdict_verify_capsule
Read-onlyIdempotent

Recompute the hash of a supplied frozen capsule. A matching hash proves internal integrity only, not source truth, SML issuance, receipt authenticity, Jev execution or payment. No model or wallet call.

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": {
      "capsule": "<capsule>"
    },
    "name": "verdict_verify_capsule"
  }
}

Input Schema

NameRequiredDescriptionDefault
capsuleYesA frozen decision capsule as produced by verdict_compile_capsule, including its version, timestamp and hash. The tool recomputes the hash over the supplied capsule and reports whether it matches.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / capsule / description
      Added value: +"A frozen decision capsule as produced by verdict_compile_capsule, including its version, timestamp and hash. The tool recomputes the hash over the supplied capsule and reports whether it matches."
  2. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds real value beyond that: 'No model or wallet call' tells the agent there are no external side effects or network dependencies, and the caveat about what a matching hash does and does not prove prevents the agent from over-trusting the result. It stops short of stating the exact return shape.

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 sentences, front-loaded with the action and followed by the critical scope limitation. Every clause carries information — the hash recomputation, the integrity-only boundary, and the absence of model/wallet calls — with no filler.

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 single-parameter, non-destructive verification tool with a fully annotated nested schema, the description covers the essentials: what it does, what a positive result means and does not mean, and that no external calls occur. Since there is no output schema, it would be slightly stronger if it explicitly stated that the response is a match/no-match verdict.

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?

There is a single parameter with 100% schema description coverage, including a nested object whose fields are individually typed, constrained and described. The description adds no parameter-level detail beyond the schema, so the baseline 3 applies.

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 opens with a specific verb and resource: 'Recompute the hash of a supplied frozen capsule.' It also scopes the claim precisely by distinguishing internal integrity from source truth, issuance, receipt authenticity and execution, which lets an agent separate this from verdict_compile_capsule (which produces the capsule) without opening either 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?

Usage context is clear: call this when you have a frozen capsule and need to check it has not been altered. The description supplies an explicit when-not list ('not source truth, SML issuance, receipt authenticity, Jev execution or payment'), which is strong negative guidance. It does not name a sibling alternative for those other verification needs, so it falls short of a 5.

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