Skip to main content
Glama

SCRIPTMASTERLABS — Verdict Protocol

Review supplied Jev jury votes

verdict_review_jury
Read-onlyIdempotent

Validate five uniquely identified caller-supplied juror votes and recompute the production jury aggregation. No new Jev evaluation occurs. The report is untrusted input: aggregation does not authenticate issuance, correctness, independence, trade approval or payment.

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>",
      "votes": "<votes>"
    },
    "name": "verdict_review_jury"
  }
}

Input Schema

NameRequiredDescriptionDefault
votesYesExactly five caller-supplied juror votes — one per juror (CAUSAL, HISTORIAN, SKEPTIC, MICROSTRUCTURE, TAIL_RISK) — each with a decision (PROCEED | WAIT | NO_TRADE), probability, confidence, and the model name. The jury aggregation is recomputed from these votes; they are treated as untrusted input.
capsuleYesThe frozen decision capsule the supplied juror votes were cast on, including its version, timestamp and hash.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / capsule / description
      Added value: +"The frozen decision capsule the supplied juror votes were cast on, including its version, timestamp and hash."
    • addedInput schema / properties / votes / description
      Added value: +"Exactly five caller-supplied juror votes — one per juror (CAUSAL, HISTORIAN, SKEPTIC, MICROSTRUCTURE, TAIL_RISK) — each with a decision (PROCEED | WAIT | NO_TRADE), probability, confidence, and the model name. The jury aggregation is recomputed from these votes; they are treated as untrusted input."
  2. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description then adds real value beyond that with a trust boundary: aggregation does not authenticate issuance, correctness, independence, trade approval or payment, so the agent knows the output must not be treated as verified. The one weakness is the opaque phrase 'The report is untrusted input,' which does not specify what report is meant.

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?

Three short sentences, front-loaded with the action and immediately followed by the scope exclusion and the trust caveat. No filler, no repetition of schema or annotation content.

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 tool with a nested vote array and no output schema, the description covers the action, the input provenance, the recomputation target, and the trust limits. It stops short of describing what the recomputed aggregation response contains, which matters somewhat given there is no output schema to fall back on.

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 baseline is 3. The description adds meaning beyond the schema by stating the votes must be 'uniquely identified' — a one-per-juror uniqueness constraint the schema's minItems/maxItems of 5 does not enforce — and by reiterating that the supplied votes are untrusted. It says nothing extra about the capsule beyond what its schema description already covers.

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 pairs a specific verb with a specific resource: validate five caller-supplied juror votes and recompute the jury aggregation, with the explicit negative scope 'No new Jev evaluation occurs.' That cleanly separates it from an evaluation-running tool, though it never names the sibling (e.g. verdict_decide) it is distinguished from, leaving the agent to infer the routing.

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 phrase 'No new Jev evaluation occurs' plus 'caller-supplied' establishes the situation clearly: use this when votes already exist externally and only the aggregation needs recomputing. However, there is no explicit statement of when NOT to use it or which sibling to call instead for a fresh evaluation or capsule verification.

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