Skip to main content
Glama
Sign In

ONE — pagos en Monero y trueque de cómputo

by io.github.eddyflores100-lang
OverviewDiscussionsAdmin

one_trueque_ofrecer

Publica en el libro de trueque una oferta o demanda de potencia de cálculo (GPU-h, CPU-h, RAM-GB-h, red-GB…) y qué se pide a cambio (otro recurso, XMR, trabajo).

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": {
      "tipo": "<tipo>",
      "recurso": "<recurso>",
      "cantidad": "<cantidad>",
      "cambio": "<cambio>"
    },
    "name": "one_trueque_ofrecer"
  }
}

Input Schema

NameRequiredDescriptionDefault
peerNoContraparte sugerida (opcional)
tipoYesOfrezco o busco
cambioYesQué se pide a cambio
recursoYesRecurso: GPU-h, CPU-h, RAM-GB-h, red-GB, almacenamiento-GB…
cantidadYesCantidad del recurso
valida_hNoVigencia en horas (por defecto 72)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/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 burden of behavioral disclosure. 'Publica' implies a write operation, but the description does not explain permissions, visibility, whether the listing can later be edited or cancelled, default validity, or what the publication returns. It communicates the content being posted but not the behavioral consequences.

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 a single front-loaded sentence with no filler. It efficiently states the action, the medium, the resource category, and the exchange concept.

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 write-oriented tool with no annotations and no output schema, the description is minimally adequate: it defines the core action and content, and the schema covers all parameters. However, it omits important behavioral context such as what publication entails, whether the offer is immediately live, and what an agent should expect after calling it.

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%, so the input schema already documents all six parameters, including the tipo enum and valida_h default. The description adds conceptual framing around 'recurso' and 'cambio' but does not add syntax, format, or constraints beyond what the schema provides.

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 states a specific verb and resource: publishing an offer or demand for compute power into the barter book, with examples of resources and what is requested in exchange. This clearly distinguishes it from sibling tools like one_trueque_listar and one_trueque_cerrar, which imply listing and closing rather than publishing.

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 description explains what the tool does but gives no guidance on when to use it versus alternatives, nor any prerequisites or exclusions. An agent must infer that this is the tool for creating a new barter listing, with no explicit routing or context.

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

All ONE — pagos en Monero y trueque de cómputo toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources