Skip to main content
Glama

defense-gateway

arbitrate_dispute

Resuelve disputas de contratos de custodia auditando la cadena Multi-CaMeL (Why-Trail).

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": {
      "contract_id": "<contract_id>"
    },
    "name": "arbitrate_dispute"
  }
}

Input Schema

NameRequiredDescriptionDefault
contract_idYes
claimed_evidence_hashNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.7/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden. It says the tool audits the Multi-CaMeL chain but does not disclose whether it issues a binding resolution, mutates dispute state, what permissions or evidence are required, or whether the outcome is reversible — material for an arbitration tool.

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?

One sentence, front-loaded with the action and followed by the method — no filler. It is terse to the point of under-specification, but nothing in it is wasted.

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

Completeness2/5

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

For a tool with two undocumented parameters, no annotations, and no output schema, the description gives only a one-line purpose. An agent cannot tell what it will receive back, what state changes occur, or what a valid call requires.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% and neither parameter is mentioned in the description. The meaning and format of contract_id and especially claimed_evidence_hash (how a hash is computed, what happens if it mismatches the chain) are left entirely undefined.

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 names a specific verb and resource ('Resuelve disputas de contratos de custodia') plus the mechanism used ('auditando la cadena Multi-CaMeL (Why-Trail)'), so an agent knows what the tool does and how. It does not, however, distinguish itself from audit/ruling siblings such as request_epistemic_audit or verify_normative_validity.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no guidance on when to invoke this tool versus the audit or verification siblings, no stated preconditions (e.g., must a dispute already be filed?), and no exclusions. The agent must infer the trigger condition from the name alone.

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.