Skip to main content
Glama

Read deal status

get_deal_status
Read-onlyIdempotent

Reads an on-chain escrow deal by ID and decodes public fields, deadlines, and a read-only hint about who can act next; unknown IDs return not_found.

Instructions

Read deals(bytes32) with eth_call and decode the public deal fields, deadlines and a read-only hint about who can act next. An unknown id returns not_found. Does not sign or send.

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": {
      "deal_id": "<deal_id>"
    },
    "name": "get_deal_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
chainNoMust match this process. Defaults to the configured chain.
escrowNoDefaults to v2. v1-legacy is read-only and only on Arbitrum One.
deal_idYes0x-prefixed 32-byte deal id.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/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 open-world, so the bar is lower. The description still adds real substance: the eth_call mechanism, the decoded payload contents, and the unknown-id error path returning 'not_found' — the kind of failure behavior annotations cannot express.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two tight sentences with the resource and mechanism front-loaded, the return content next, and the error and safety limits last. No sentence is redundant or padding.

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 must sketch return shape, and it does: deal fields, deadlines, and a read-only actor hint. Safety is covered by annotations and the error case is named, leaving only field-level detail of the decoded struct unstated.

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% (all three params documented, including the two enums and the bytes32 format), so the schema carries the load. The description's 'deals(bytes32)' restates the schema's own '0x-prefixed 32-byte deal id' rather than adding new meaning about chain or escrow selection.

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?

States a specific verb and resource ('Read deals(bytes32) with eth_call') plus exactly what it returns: public deal fields, deadlines, and a next-actor hint. The closing 'Does not sign or send' implicitly separates it from write-path siblings like prepare_deal.

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?

Usage is implied rather than stated: it is clearly the read path for a deal, and 'Does not sign or send' signals when not to reach for it. However, no alternative sibling is named and there is no explicit prerequisite or condition that picks this over another call.

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

Deploy Server

Other Tools