Skip to main content
Glama

A2A Defense & Monetization Gateway

create_escrow_deposit

Crea un contrato de custodia colateralizado con bloqueo de fondos y colateral del proveedor.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "client_id": "<client_id>",
      "provider_id": "<provider_id>",
      "service_fee": "<service_fee>",
      "provider_stake": "<provider_stake>"
    },
    "name": "create_escrow_deposit"
  }
}

Input Schema

NameRequiredDescriptionDefault
client_idYes
provider_idYes
service_feeYes
provider_stakeYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.7/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full burden. It does disclose two real behavioral facts — funds get blocked and provider collateral is taken — which is more than nothing. But for a financial mutation it says nothing about whether funds move immediately, how long the lock lasts, who can release it, whether it is reversible, or what permissions/signatures are required.

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?

A single front-loaded sentence with no filler or repetition. It is efficient, though the brevity is partly a symptom of under-specification rather than disciplined editing.

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?

For a four-parameter financial mutation with no annotations, no output schema, and no parameter documentation, this is thin. The agent knows what it creates but not the preconditions, the side effects on funds, or what a successful call returns.

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

Parameters2/5

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

Schema description coverage is 0% across four required parameters, so the description must compensate and largely does not. The phrases 'bloqueo de fondos' and 'colateral del proveedor' loosely gesture at service_fee and provider_stake, but client_id and provider_id are never addressed, and no units, currency, or boundary conditions are given for the integer amounts.

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

Purpose4/5

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

The description pairs a specific verb ('Crea') with a specific resource ('contrato de custodia colateralizado'), and adds two defining traits: funds are locked and the provider posts collateral. That is enough to distinguish it from the unrelated siblings in the catalog, though it does not name any alternative by name.

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?

There is no guidance on when to create an escrow versus when not to, no prerequisites (who must be party to it, what state the client/provider must be in), and no mention of alternatives. The agent must infer the usage context entirely from the tool name.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources