Skip to main content
Glama

ONE — pagos en Monero y trueque de cómputo

one_trueque_cerrar

Cierra un trueque del libro registrando la contraparte con la que se pactó.

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": {
      "id": "<id>",
      "contraparte": "<contraparte>"
    },
    "name": "one_trueque_cerrar"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesId del trueque (TRQ-…)
contraparteYesCon quién se cierra

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden for a mutation tool. It states that closing registers the counterparty but does not disclose whether the operation is irreversible, what state changes occur, whether permissions are required, or what happens if the trade is already closed.

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?

The definition is a single front-loaded sentence with no wasted wording. It is appropriately concise, though its brevity contributes to the gaps in guidance and behavioral context.

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 mutation tool with no annotations and no output schema, the description is too thin. It does not explain the result of closing, the expected prior state, or side effects, leaving an agent with insufficient context to invoke it confidently.

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%, so both parameters are already documented as "id" and "contraparte" with their types. The description slightly reinforces "contraparte" as the party with whom the trade was agreed, but adds no format, validation, or syntax details beyond the schema.

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 uses a specific verb ("Cierra") and resource ("un trueque del libro") and adds the action of registering the counterparty. It clearly distinguishes closing a trade from siblings like offering or listing, although it does not explicitly name an alternative tool.

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 phrase "con la que se pactó" hints that the trade must already be agreed, but there is no explicit when-to-use guidance, prerequisites, or when-not-to-use condition. No alternative or sibling tool is referenced to help the agent choose correctly.

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.