Skip to main content
Glama

spraay_escrow_fund

Changes an escrow's status from 'created' to 'funded'. Works only on unfunded, non-expired escrows and costs $0.002 USDC.

Instructions

Mark an escrow as funded. Changes status from 'created' to 'funded'. Only works on unfunded, non-expired escrows. Data persists in Supabase. Costs $0.002 USDC.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
escrowIdYesEscrow ID to fund (e.g. 'ESC-A1B2C3D4E5F6')

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
okYesTrue when the gateway call succeeded; false when it returned an error.
dataNoThe gateway response payload on success. The exact shape depends on the tool (see the tool description and the JSON in the text content block).
errorNoHuman-readable error message, present only when ok is false.
Behavior4/5

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

Discloses that data persists in Supabase and costs $0.002 USDC, which are important behavioral traits beyond annotations. Annotations only provide readOnlyHint; description adds cost and persistence context.

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?

Three concise sentences, each serving a purpose: purpose, precondition, and additional context (persistence, cost). No unnecessary information.

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?

Covers purpose, precondition, persistence, and cost. With output schema existing, return values need not be explained. Complete for a simple state-change tool.

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 coverage is 100% and schema already describes escrowId with an example. Description does not add extra parameter semantics beyond what's in the schema.

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?

Clear verb 'Mark as funded' and purpose stated. Distinguishes from escrow siblings (create, cancel, release) by specifying the specific status change from 'created' to 'funded'.

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?

Explicit precondition: 'Only works on unfunded, non-expired escrows.' Does not explicitly mention alternatives, but context among siblings makes it clear when to use this tool.

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/plagtech/spraay-x402-mcp'

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