Skip to main content
Glama

textokit_bcra_indicadores

Indicadores monetarios del BCRA. 0.002 USDC per call (x402, Base), first 10 calls/day per IP free; an unpaid call returns the x402 payment requirements. Free sample: textokit_sample.

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": {
      "resource": "<resource>"
    },
    "name": "textokit_bcra_indicadores"
  }
}

Input Schema

NameRequiredDescriptionDefault
desdeNoOptional serie-only start date, YYYY-MM-DD; must not exceed…
hastaNoOptional serie-only end date, YYYY-MM-DD.
limitNoRequested page size, 1–20; defaults to 5.
queryNoOptional lista-only text filter within the received page;…
offsetNoRequested page offset; defaults to 0.
resourceYeslista returns variables; serie returns observations for one…
idVariableNoRequired for serie; forbidden for lista. Positive BCRA…
payment_signatureNoOptional, legacy: base64 x402 v2 payment payload. Preferred: params._meta["x402/payment"]. Never a private key.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / payment_signature / description
      Previous value: -"Optional base64 x402 v2 payment payload for the requirements of a prior unpaid call. Never a private key."New value: +"Optional, legacy: base64 x402 v2 payment payload. Preferred: params._meta[\"x402/payment\"]. Never a private key."
  2. Changed5 schema fields changed
    • changedInput schema / properties / desde / description
      Previous value: -"Optional serie-only start date, YYYY-MM-DD; must not exceed hasta."New value: +"Optional serie-only start date, YYYY-MM-DD; must not exceed…"
    • changedInput schema / properties / idVariable / description
      Previous value: -"Required for serie; forbidden for lista. Positive BCRA variable ID."New value: +"Required for serie; forbidden for lista. Positive BCRA…"
    • changedInput schema / properties / payment_signature / description
      Previous value: -"Optional. Base64 x402 v2 payment payload signed by YOUR wallet for the requirements returned by a previous unpaid call. Never a private key."New value: +"Optional base64 x402 v2 payment payload for the requirements of a prior unpaid call. Never a private key."
    • changedInput schema / properties / query / description
      Previous value: -"Optional lista-only text filter within the received page; matches ID, description and category without case or accent distinctions."New value: +"Optional lista-only text filter within the received page;…"
    • changedInput schema / properties / resource / description
      Previous value: -"lista returns variables; serie returns observations for one variable."New value: +"lista returns variables; serie returns observations for one…"
  3. First observed

TDQS

B3.1/5.0
Behavior4/5

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

With zero annotations the description carries the full burden, and it discloses genuinely non-obvious behavior: price (0.002 USDC on Base), a free tier of 10 calls/day per IP, and that an unpaid call returns x402 payment requirements rather than an error. It does not say what the response looks like or whether calls are read-only, but the payment/access model is well covered.

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?

Three short sentences, purpose front-loaded, pricing and sample-tool pointer following with no filler. Slightly awkward that access/payment terms occupy more space than the actual capability.

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 an eight-parameter, two-mode data tool with no output schema and no annotations, the description explains access terms but not the shape of the data returned or the lista-versus-serie distinction. An agent can call it correctly using the schema, but not predict what comes back.

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 all eight parameters including the lista/serie enum and the serie-only desde/hasta/idVariable constraints are already documented in structured fields. The description adds nothing about parameters, which is acceptable under the high-coverage baseline but earns no uplift.

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

Purpose3/5

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

The description names the resource ('Indicadores monetarios del BCRA') but supplies no verb and no indication of what is actually returned, so an agent must open the schema to learn that the tool serves two distinct modes (lista of variables vs serie of observations). It is enough to distinguish this from siblings like dolar_ar or fx_rates, but barely.

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 pick this over textokit_dolar_ar, textokit_fx_rates, or textokit_normativa_ar. The only routing hint is 'Free sample: textokit_sample', which addresses payment logistics rather than tool selection, and no exclusions or prerequisites are stated.

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.