Skip to main content
Glama
CSOAI-ORG

Agent Commerce Payments MCP

by CSOAI-ORG
OverviewSchemaRelated ServersScoreDiscussions
Python
Remote

escrow_funds

Hold funds securely between two agents until predefined conditions are met, with automatic expiry.

Instructions

Place funds in escrow between two agents with conditions and expiry.

Behavior: This tool is read-only and stateless — it produces analysis output without modifying any external systems, databases, or files. Safe to call repeatedly with identical inputs (idempotent). Free tier: 10/day rate limit. Pro tier: unlimited. No authentication required for basic usage.

When to use: Use this tool when you need structured analysis or classification of inputs against established frameworks or standards.

When NOT to use: Not suitable for real-time production decision-making without human review of results.

Args: agent_a (str): The agent a to analyze or process. agent_b (str): The agent b to analyze or process. amount (float): The amount to analyze or process. currency (str): The currency to analyze or process. condition (str): The condition to analyze or process. expiry_hours (int): The expiry hours to analyze or process. api_key (str): The api key to analyze or process.

Behavioral Transparency: - Side Effects: This tool is read-only and produces no side effects. It does not modify any external state, databases, or files. All output is computed in-memory and returned directly to the caller. - Authentication: No authentication required for basic usage. Pro/Enterprise tiers require a valid MEOK API key passed via the MEOK_API_KEY environment variable. - Rate Limits: Free tier: 10 calls/day. Pro tier: unlimited. Rate limit headers are included in responses (X-RateLimit-Remaining, X-RateLimit-Reset). - Error Handling: Returns structured error objects with 'error' key on failure. Never raises unhandled exceptions. Invalid inputs return descriptive validation errors. - Idempotency: Fully idempotent — calling with the same inputs always produces the same output. Safe to retry on timeout or transient failure. - Data Privacy: No input data is stored, logged, or transmitted to external services. All processing happens locally within the MCP server process.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
amountYes
agent_aYes
agent_bYes
api_keyNo
currencyNoGBP
conditionNo
expiry_hoursNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Tool Definition Quality

D1.9/5.0
Behavior2/5

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

Although the description includes a detailed 'Behavioral Transparency' section, it incorrectly claims the tool is read-only and idempotent, which contradicts the escrow action. This misleads the agent about side effects and state changes.

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

Conciseness2/5

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

The description is repetitive (e.g., the 'Behavior' bullet list and the 'Behavioral Transparency' section overlap) and contains boilerplate that does not earn its place. Shorter, tool-specific content would be more effective.

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

Completeness2/5

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

Despite having an output schema and sibling tools, the description fails to explain how the escrow works, what the output contains, or how to use the tool correctly. The generic analysis framing is incomplete for a financial escrow operation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 0% schema description coverage, the description must compensate but only provides generic, unhelpful descriptions like 'The agent a to analyze or process.' No specifics about parameters like 'condition', 'expiry_hours', or 'currency' in the context of escrow are given.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The first sentence 'Place funds in escrow between two agents with conditions and expiry' clearly indicates a financial action, but subsequent statements claim it is 'read-only and stateless' producing 'analysis output', creating a major contradiction that undermines purpose clarity.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The 'When to use' and 'When NOT to use' sections are generic and seem copied from a different tool (e.g., 'structured analysis or classification'). They do not differentiate from sibling tools like 'release_escrow' or provide context for using this escrow tool specifically.

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/CSOAI-ORG/agent-commerce-payments-mcp'

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