Skip to main content
Glama
Sign In

Escro

by ai.escro
OverviewDiscussionsAdmin

List escrows

list_escrows
Read-onlyIdempotent

List escrows on escro.ai with optional filters: state (one of the 8 lifecycle states), assignedTo (base-58 worker wallet), mine (true: only escrows this server's wallet created as the buyer; refused on a server with no wallet), limit (1-100; the API returns 20 by default) and offset for pagination. Call get_escrow for a single escrow. Read-only; needs no wallet except for mine.

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": "list_escrows"
  }
}

Input Schema

NameRequiredDescriptionDefault
mineNotrue: only escrows this server's wallet created (it is the buyer)
limitNoPage size, 1-100; the API returns 20 when omitted
stateNoReturn only escrows in this lifecycle state
offsetNoNumber of escrows to skip
assignedToNoBase-58 wallet; return only escrows assigned to this worker

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds non-annotation context: the wallet requirement ("needs no wallet except for mine") and the server-side refusal for mine, which an agent cannot infer from the schema. Return shape is not described, but that is a minor gap here.

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 filter list is front-loaded and every clause carries information; the alternative-pointer and read-only note are short trailing sentences. The single long enumerated sentence is dense but readable, with only the default-20 remark being redundant with the schema.

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 read-only list tool with full schema coverage and no output schema, the description covers filters, defaults, pagination, wallet prerequisites and the single-record alternative. It could say what the response envelope looks like (array vs paged object), which is the only meaningful omission.

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?

Schema coverage is 100%, so the baseline is 3; the description earns above that by adding semantics the schema lacks — that state is one of 8 lifecycle states, and that mine is refused on a wallet-less server. The limit/default-20 note duplicates the schema, so it does not add further value.

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 ("List escrows on escro.ai") plus the full filter surface, and explicitly contrasts with the sibling get_escrow. An agent can distinguish this from get_escrow without opening either schema.

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?

Explicitly routes single-record lookups to get_escrow and warns that mine is refused on a server with no wallet, which is a real when-not condition. It does not spell out guidance for choosing between filter combinations (e.g. state vs assignedTo), but the usage context is clear.

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

All Escro 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