Skip to main content
Glama

swarmtrade_resolve_dispute

Resolve escrow disputes by releasing funds to the seller or refunding the buyer. Choose resolution type for the disputed escrow.

Instructions

Resolve a disputed escrow by releasing funds to the seller or refunding the buyer. This is irreversible.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
escrow_idYesThe escrow ID with an active dispute
resolutionYes"release" sends funds to seller, "refund" returns funds to buyer
Behavior4/5

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

With no annotations, the description carries the full burden. It explicitly states the operation is 'irreversible', a critical behavioral trait. However, it does not disclose who can resolve (e.g., arbitrator only) or any confirmation steps.

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?

The description is extremely concise with two sentences, no redundant information, and front-loads the core action.

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 two-parameter tool with no output schema, the description covers the essential action and irreversible nature. It could mention that the escrow must be in dispute state, but it is implied. Adequate but not exhaustive.

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%, and the description adds minimal meaning beyond the schema: it rephrases the enum values. Baseline 3 is appropriate since the schema already fully explains parameters.

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?

The description clearly states the verb 'resolve' and the resource 'disputed escrow', specifying two possible outcomes: releasing funds to seller or refunding buyer. It effectively distinguishes from sibling 'swarmtrade_dispute_trade', which initiates a dispute.

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?

The description implies the tool is for disputed escrows, providing clear context for when to use it. It does not explicitly mention when not to use or reference alternatives, but the context is sufficient for an AI agent to infer proper usage.

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/tjcrowley/swarmtrade'

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