Skip to main content
Glama

SCRIPTMASTERLABS — Verdict Protocol

Compile a decision capsule

verdict_compile_capsule
Read-only

Freeze caller-supplied research state into a timestamped SHA256 capsule using the production compiler. Stateless: no persistence, Jev call, signature, paid receipt, trade approval or settlement. The timestamp changes each compilation.

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

Input Schema

NameRequiredDescriptionDefault
capsuleYesThe decision capsule to freeze: instrument, regime, thesis (LONG_CANDIDATE | SHORT_CANDIDATE | NEUTRAL), support and contradiction scores, and execution eligibility (ELIGIBLE | INELIGIBLE), plus optional metadata. The compiler timestamps it and computes its SHA-256 hash.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / capsule / description
      Added value: +"The decision capsule to freeze: instrument, regime, thesis (LONG_CANDIDATE | SHORT_CANDIDATE | NEUTRAL), support and contradiction scores, and execution eligibility (ELIGIBLE | INELIGIBLE), plus optional metadata. The compiler timestamps it and computes its SHA-256 hash."
  2. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare read-only, non-destructive, closed-world and non-idempotent, and the description adds real value beyond them: it is stateless with no persistence, and the timestamp changes on every compilation, which explains the non-idempotent hint. The enumerated non-effects (no signature, receipt, approval, settlement) also set accurate expectations. It does not mention auth or rate-limit behavior, so it is not a 5.

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 tight sentences with the core action front-loaded and the negative scope following. Minor deductions for the unexplained jargon term 'Jev call' and the dense run-on enumeration of non-effects, which an agent must parse without context.

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

Completeness3/5

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

There is no output schema, so the description should say what the caller receives — the hash, the timestamp, the capsule, or all three. It implies a timestamped SHA-256 capsule is produced but does not specify the return shape. For a stateless single-parameter computation this is an adequate but incomplete definition.

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 description coverage is 100% and the nested capsule schema documents every field, including enums for thesis and execution, so the schema carries the parameter burden. The description only restates that the capsule is caller-supplied research state that gets timestamped and hashed, adding no field-level meaning.

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 gives a specific verb and resource: freeze caller-supplied research state into a timestamped SHA-256 capsule via the production compiler. That is concrete enough to distinguish compiling a capsule from verifying one. It stops short of naming how it differs from siblings such as verdict_verify_capsule or verdict_decide.

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?

Usage is implied by the strong negative scope (no persistence, no signature, no trade approval), which tells an agent this is a pure computation rather than a workflow step. However, there is no explicit statement of when to call this instead of verdict_verify_capsule or verdict_decide, and no prerequisites or ordering guidance.

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