viridis-agent-fleet

Overview Schema Source Related Servers Discussions Admin

escrow__list_escrows

List escrows from a trustless escrow system, optionally filtered by state such as OPEN, FUNDED, or DISPUTED.

Instructions

[escrow — trustless escrow & settlement (exactly-once)] List escrows, optionally filtered by state (OPEN|FUNDED|RELEASED|REFUNDED|DISPUTED).

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

Input Schema

Name	Required	Description	Default
`state`	No

Schema Changelog

Changes observed during successful MCP inspections.

Addedv0.1.12Jul 28, 2026
Removedv0.1.11Jul 18, 2026
Changed6 schema fields changedv0.1.9Jul 16, 2026
- removedInput schema / properties / state / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- removedInput schema / properties / state / default
```
Removed value: -null
```
- removedInput schema / properties / state / title
```
Removed value: -"State"
```
- addedInput schema / properties / state / type
```
Added value: +"string"
```
- addedInput schema / required
```
Added value: +[]
```
- removedInput schema / title
```
Removed value: -"list_escrowsArguments"
```
Changed6 schema fields changedJul 13, 2026
- addedInput schema / properties / state / anyOf
```
Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
```
- addedInput schema / properties / state / default
```
Added value: +null
```
- addedInput schema / properties / state / title
```
Added value: +"State"
```
- removedInput schema / properties / state / type
```
Removed value: -"string"
```
- removedInput schema / required
```
Removed value: -[]
```
- addedInput schema / title
```
Added value: +"list_escrowsArguments"
```
Changed6 schema fields changedJul 13, 2026
- removedInput schema / properties / state / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- removedInput schema / properties / state / default
```
Removed value: -null
```
- removedInput schema / properties / state / title
```
Removed value: -"State"
```
- addedInput schema / properties / state / type
```
Added value: +"string"
```
- addedInput schema / required
```
Added value: +[]
```
- removedInput schema / title
```
Removed value: -"list_escrowsArguments"
```
First observedJul 13, 2026

TDQS

A3.6/5.0

Behavior2/5

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

No annotations; description only mentions basic listing and filtering. Lacks details on pagination, sorting, default behavior, or any side effects.

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?

Two sentences; the prefix tag adds some clutter but the core description is clear and efficient.

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

Completeness3/5

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

For a simple list tool with one optional parameter, description covers main functionality. Missing details on pagination, result set limits, or return format, but overall adequate.

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 has 0% description coverage, but description lists the parameter and enumerates possible state values (OPEN, FUNDED, RELEASED, REFUNDED, DISPUTED), adding meaning beyond the schema's raw string type.

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?

Clearly states 'List escrows' with optional state filter, and lists all possible state values. Distinguishes from sibling escrow mutation 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?

Implies use when you need to list escrows, but no explicit when-to-use, when-not-to-use, or comparison with siblings like escrow__escrow_status.

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

Deploy Server