Skip to main content
Glama
Sign In

Consignatarias · Argentine Cattle Market

by ar.com.consignatarias
OverviewDiscussionsAdmin

PRO Consignataria: cotizar y activar en USDC

subscribe_broker_pro
Read-onlyIdempotent

Cotiza y explica cómo activar PRO Consignataria, el plan del SITIO WEB consignatarias.com.ar, pagando en USDC (x402). Lo que incluye vale en el sitio y en el newsletter, no en este servidor: sello ★ PRO y lugar destacado en los listados web y en la portada; remates resaltados en el calendario y en sus fichas; lugar destacado en el newsletter semanal con registro de envíos; leads con nombre y contacto; panel con quién mira el perfil, cuándo y desde dónde (incluidas visitas desde IAs); cruce contra el Mercado de Cañuelas si opera ahí. Mismo producto que en /planes (ARS 45.000/mes), cotizado al dólar blue del día. Esta tool NO cobra: devuelve el monto exacto y el endpoint x402 para pagar. Las respuestas de este servidor MCP no cambian con el plan: find_livestock_broker y las demás tools no ordenan ni marcan por pago. Params: slug (consignataria del directorio, usá find_livestock_broker si no lo sabés), meses (1-12, default 1). [EN] Quote and subscribe to the PRO plan for a livestock broker profile, payable in USDC.

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": {
      "slug": "<slug>"
    },
    "name": "subscribe_broker_pro"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesSlug de la consignataria en el directorio
mesesNoMeses a contratar (1-12, default 1)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior4/5

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

Adds substantial context beyond the readOnly/idempotent annotations: it explicitly says the tool does NOT charge, that it returns the exact amount plus the x402 endpoint, and that MCP responses are unaffected by purchase. Minor gap: it doesn't say whether the x402 payment step is executed elsewhere or what the returned amount looks like, so an agent must infer the post-quote flow.

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

Conciseness3/5

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

Front-loaded and organized, but the long inventory of plan benefits (badge, listings, auctions, newsletter, leads, panel, Mercado de Cañuelas cross-check) is marketing copy that an agent doesn't need to select or invoke the tool. The critical operational facts – no charge, returns amount plus x402 endpoint, params – are buried mid-paragraph.

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

Completeness5/5

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

For a two-parameter, no-output-schema tool, everything an agent needs is present: what it returns, that it does not charge, how to source the slug, and that purchase has no effect on other tools' behavior. Nothing material is left out.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, and the description earns a bump by explaining what the slug refers to (a directory broker) and how to obtain it. The meses range (1-12, default 1) merely restates the schema, which keeps it from a 5.

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?

States a concrete verb+resource pair: quote and explain activation of the PRO plan for consignatarias.com.ar, paid in USDC via x402. It also draws a hard boundary between what this tool does (return a price and endpoint) and what it does not (charge), and names the sibling find_livestock_broker as the way to resolve the slug.

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

Usage Guidelines4/5

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

Gives explicit routing advice for the required parameter ('usá find_livestock_broker si no lo sabés') and a strong scope caveat: the benefits apply on the website and newsletter, not on this server. It never enumerates a sibling alternative for the quote/activation task itself, since none exists, so it falls just short of full when/when-not coverage.

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

All Consignatarias · Argentine Cattle Market 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