ONE — pagos en Monero y trueque de cómputo

Each tool targets a fairly distinct operation: invoicing, status, outbound payment, listing, and three barter operations. The main risk is one_cobrar vs one_pagar, which differ only by money direction (charging vs paying) and require reading the descriptions to separate. one_pagos_listar also mixes invoices and payments, but since it is the only listing tool for money it does not overlap with anything else.

The 'one_' prefix is applied uniformly, but the structure after it varies: verb-only (one_cobrar, one_pagar), noun-only (one_estado), noun_verb (one_trueque_ofrecer, one_trueque_cerrar), and plural-noun_verb (one_pagos_listar). Readable but no single predictable pattern, so an agent cannot reliably guess a name.

Seven tools is well within a comfortable range and each one maps to a concrete operation (invoice, pay, list, status, and the three barter actions). Nothing looks like filler or a redundant wrapper around another tool.

Both domains have partial lifecycles: invoices can be created and listed but there is no get-by-id, mark-as-paid, or void, and payments can be sent and listed but not queried individually. The barter book covers offer/list/close but has no cancel or update, leaving agents with dead ends for corrections and single-record lookups.