Skip to main content
Glama

SCRIPTMASTERLABS — Verdict Protocol

Verdict API contract

verdict_contract
Read-onlyIdempotent

Read the live Verdict Protocol OpenAPI contract and separate paid HTTP service requirements. This tool never calls /decide or /seal and cannot authorize payments or forward keys. Paid HTTP tiers: /decide is $0.25 USDC, /seal is $0.01 USDC, /evidence is $0.05 USDC and /dispute is $0.25 USDC via x402 on Base and Arc.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "verdict_contract"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/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 bar is lower. The description adds real context beyond them: it disclaims payment authorization and key forwarding, and discloses per-endpoint pricing and the x402/Base/Arc payment rails. That is meaningful behavioral disclosure an agent could not infer from the annotations.

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 sentences, purpose front-loaded before the exclusions and pricing detail. The pricing enumeration is dense but each item maps to a distinct endpoint cost, so it earns its place. Minor verbosity in the 'separate paid HTTP service requirements' phrasing keeps it from a 5.

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 zero-parameter, read-only, annotation-covered tool with no output schema, the description covers purpose, exclusions, and pricing adequately. It does not describe the shape or size of the returned contract, but that gap is minor given the tool's simplicity.

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?

The tool takes zero parameters, so the schema baseline is 4. The description correctly offers no parameter semantics, which is appropriate, and nothing about parameters is misleading.

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 ('Read the live Verdict Protocol OpenAPI contract') and clarifies it also surfaces paid HTTP service requirements. It also carves out what it is not by declaring it never calls /decide or /seal, which helps distinguish it from the action-oriented siblings like verdict_decide. The phrase 'separate paid HTTP service requirements' is slightly ambiguous but does not obscure the core purpose.

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?

Provides useful negative guidance (never calls /decide or /seal, cannot authorize payments or forward keys), which implicitly routes an agent away from this tool when it wants a decision or seal. However, it never explicitly names which sibling to use instead, nor gives a positive 'use this when you need the contract/pricing' condition. Usage is implied rather than spelled out.

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