Skip to main content
Glama

SCRIPTMASTERLABS — Verdict Protocol

Run paid BYOK Jev verdict

verdict_decide

Invoke the existing /decide service: five Jev jurors over a frozen capsule, with persisted signed receipt. Without payment returns the fresh x402 challenge. Requires caller Jev key in X-JEV-API-KEY and a caller-created PAYMENT-SIGNATURE header or payment_signature argument. Never creates a wallet signature or submits trades. model_spend_authorized=true is required before paid execution. Paid: $0.25 USDC via x402 on Base.

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

Input Schema

NameRequiredDescriptionDefault
capsuleYesThe decision capsule to submit for a paid verdict — the same capsule shape verdict_compile_capsule accepts: instrument, regime, thesis, support, contradiction, execution, and optional metadata.
payment_signatureNoCaller-created x402 PAYMENT-SIGNATURE value for the $0.25 USDC payment on Base; it may instead be sent as the PAYMENT-SIGNATURE HTTP header. Omit it to receive the fresh 402 payment challenge.
model_spend_authorizedNoMust be true: the caller's explicit authorization to spend on the paid Jev jury evaluation. Paid execution is refused without it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / capsule / description
      Added value: +"The decision capsule to submit for a paid verdict — the same capsule shape verdict_compile_capsule accepts: instrument, regime, thesis, support, contradiction, execution, and optional metadata."
    • addedInput schema / properties / model_spend_authorized / description
      Added value: +"Must be true: the caller's explicit authorization to spend on the paid Jev jury evaluation. Paid execution is refused without it."
    • addedInput schema / properties / payment_signature / description
      Added value: +"Caller-created x402 PAYMENT-SIGNATURE value for the $0.25 USDC payment on Base; it may instead be sent as the PAYMENT-SIGNATURE HTTP header. Omit it to receive the fresh 402 payment challenge."
  2. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already flag a non-read-only, open-world, non-idempotent call; the description adds material context on top: caller must supply an X-JEV-API-KEY, that it never creates a wallet signature or submits trades, and the exact $0.25 USDC x402 price on Base. It does not say whether a retry triggers a second charge, which matters given idempotentHint=false.

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?

Front-loads the core action, then payment flow, then auth requirements, then safety constraints — a sensible order with no filler sentences. Density of domain jargon ('Jev jurors', 'frozen capsule', 'x402') is high but each clause carries information.

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?

With no output schema, the description does supply the return shape (signed receipt on success, 402 challenge without payment) plus auth and spend-authorization prerequisites. The only meaningful omission is retry/billing behavior for a non-idempotent paid call.

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%, so capsule, payment_signature, and model_spend_authorized are already fully documented including the header alternative and the 402 fallback. The description restates those facts rather than adding syntax or format meaning, so the baseline of 3 applies.

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?

States a specific verb and resource: invoke the /decide service to run five Jev jurors over a frozen capsule and produce a persisted signed receipt. That is clearly distinguishable from compile/verify/status siblings, though it never explicitly contrasts itself with verdict_review_jury or verdict_contract.

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?

Gives real routing context: omit payment_signature to receive the fresh 402 challenge, and paid execution only proceeds with model_spend_authorized=true. It stops short of naming a sibling tool or stating when another verdict tool would be the better choice.

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