Skip to main content
Glama
Sign In

blindoracle

by io.github.craigmbrown
OverviewDiscussionsAdmin

arbitration.dispute-settlement

Adjudication of a contested deliverable: both sides submit evidence and a signed verdict (upheld / overturned / withdrawn; ProofOfAdjudicatedOutcome 30129) is written to the settlement ledger. Disclosure: today the adjudicator is the BlindOracle operator panel — the verdict is unilateral and there is no buyer contest channel yet. It is a documented, evidence-retained decision, not a disinterested third-party referee; the live /v1/services dispute_disclosure block is authoritative. No charge if the required source cannot be fetched. (x402: $5.00 USDC per call)

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": "arbitration.dispute-settlement"
  }
}

Input Schema

NameRequiredDescriptionDefault
taskNoTask/query text for this SKU

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior5/5

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

Beyond annotations, the description discloses that the adjudicator is an operator panel, the verdict is unilateral, there is no buyer contest channel, evidence is retained, and the live dispute_disclosure block is authoritative. It also explains payment terms and the no-charge condition when the required source cannot be fetched, all without contradicting 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?

The description is dense but front-loads the core action and then provides essential caveats, pricing, and failure-policy details. Most sentences earn their place, though the disclosure could be slightly tighter.

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 high-complexity adjudication tool with no output schema, the description explains the verdict types, ledger write, proof identifier, and key adjudicator limitations. It does not detail how evidence should be submitted or the exact response shape, leaving a modest gap.

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?

The sole parameter, task, has full schema description coverage, so the schema already documents its meaning. The description does not add additional syntax or content requirements for the parameter, which is acceptable at the baseline for high schema coverage.

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 states a specific action: adjudicating a contested deliverable and writing a signed verdict to a settlement ledger. It also names the verdict outcomes and the proof type, making the operation distinguishable from evidence-gathering siblings, though it does not explicitly contrast itself with bundle.dispute-evidence or similar tools.

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?

The description implies this tool is for contested deliverables where evidence is submitted and a verdict is needed. However, it gives no explicit when-to-use versus when-not-to-use guidance or named alternatives among the many sibling tools.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All blindoracle toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources