Skip to main content
Glama

textokit_normativa_ar

Argentina Boletin Oficial search: official gazette notices with excerpts. 0.005 USDC per call (x402, Base); 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": {
      "query": "<query>"
    },
    "name": "textokit_normativa_ar"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateNoOptional publication date, YYYY-MM-DD, selecting daily mode.…
limitNoMaximum notices to read, from 1 to 10; default: 3.
queryYesNonempty keyword or search text, up to 200 UTF-16 units.
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. Changed2 schema fields changed
    • changedInput schema / properties / date / description
      Previous value: -"Optional publication date, YYYY-MM-DD, selecting daily mode. Omit for keyword search without a date; supplied dates must be valid."New value: +"Optional publication date, YYYY-MM-DD, selecting daily mode.…"
    • 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."
  3. First observed

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does disclose meaningful behavior beyond the schema: the per-call price, the x402/Base payment mechanism, the unpaid-call response (payment requirements rather than data), and the sample alternative. It omits return-shape details and rate limits, keeping it below a 5.

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?

Two short sentences, front-loaded with the resource and followed immediately by the payment and free-sample facts. No filler and nothing repeated from the schema.

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

Completeness4/5

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

Without annotations or an output schema, the description covers the crucial agent-facing concerns (cost, payment failure mode, free alternative). It leaves the returned structure only loosely implied by 'excerpts', a minor gap for a search tool.

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 schema already documents query, date, limit and payment_signature including the preferred _meta payment location. The description adds no parameter meaning beyond that, so the baseline 3 applies.

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 specific verb and resource ('Argentina Boletin Oficial search: official gazette notices with excerpts'), which no sibling covers. The scope and output nature (excerpts) are clear enough to distinguish it from textokit_cartas_ar, textokit_web_read and other siblings.

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 clear usage context: a paid call costs 0.005 USDC, an unpaid call returns x402 payment requirements, and 'Free sample: textokit_sample' names the alternative for testing. It stops short of explicit when-not-to-use guidance, but the free-sample routing covers the main alternative.

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.