Skip to main content
Glama

view_dispute

Inspect the dispute record of a contract to check arbitration vote status and payout state after resolution. Returns JSON with vote counts, resolution, and winner payment flag.

Instructions

Get the on chain dispute record for a Disputed or Resolved contract.

Use this to follow an arbitration vote and to check payout state after resolution. Fields returned:

  • frozen_n, threshold: arbitrator set size and votes needed, frozen when the dispute was filed.

  • vc_alice, vc_bob: current vote counts for the requester and the worker.

  • resolution: 0 none yet, 1 the requester (Alice) won, 2 the worker (Bob) won.

  • winner_paid: 1 once the winner has claimed. A Resolved contract stays at status 6 or 7 forever, so this flag is the ONLY signal that the payout happened. Never retry claim_funds when winner_paid is 1.

  • fee_share, fee_remainder, remainder_swept: how the dispute fee was split among the consensus voting arbitrators, and whether the remainder went to the treasury.

  • bond_encumbered: 1 while this dispute holds a lien on the worker's reputation bond (the bond cannot be reclaimed until the dispute ends).

Read only, needs no wallet funds.

Args: job_id: The contract ID whose dispute to inspect.

Returns the dispute record as JSON with a one line interpretation, or an error message.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
job_idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

With no annotations, the description fully discloses behavior: it is read-only, requires no wallet funds, explains all return fields in detail, and warns about the winner_paid flag. Exceptionally transparent.

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?

Well-structured with purpose, usage, field explanations, and return info. Slightly lengthy due to detailed field descriptions, but every sentence adds value. Front-loaded and organized.

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

Completeness5/5

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

Given the simple single-parameter tool and no output schema provided, the description covers all necessary context: input, output, behavior, safety, and warnings. Complete for this complexity level.

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

Parameters5/5

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

Only one parameter (job_id) with 0% schema description coverage. Description explains 'The contract ID whose dispute to inspect,' adding crucial meaning beyond the schema's type definition.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Description clearly states 'Get the on chain dispute record for a Disputed or Resolved contract.' Specific verb and resource, and distinguishes from sibling tools (view_contract, view_worker_reputation).

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?

Provides clear usage context: 'Use this to follow an arbitration vote and to check payout state after resolution.' Includes a caution about not retrying claim_funds when winner_paid is 1. Does not explicitly exclude alternatives but context is sufficient.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/honeytones/idios'

If you have feedback or need assistance with the MCP directory API, please join our Discord server