Skip to main content
Glama

textokit_direcciones_ar

Argentine address candidates from Georef. 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": {
      "direccion": "<direccion>"
    },
    "name": "textokit_direcciones_ar"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum returned candidates, from 1 to 10; defaults to 5.
direccionYesAddress text, from 3 to 200 characters. Locality text alone…
provinciaIdNoOptional two-digit province identifier, preserving leading…
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. Changed3 schema fields changed
    • changedInput schema / properties / direccion / description
      Previous value: -"Address text, from 3 to 200 characters. Locality text alone may not restrict results."New value: +"Address text, from 3 to 200 characters. Locality text alone…"
    • 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 / provinciaId / description
      Previous value: -"Optional two-digit province identifier, preserving leading zeros. Example: 02 for CABA."New value: +"Optional two-digit province identifier, preserving leading…"
  3. First observed

TDQS

B3.4/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses cost (0.002 USDC per call), network (x402, Base), a free tier (10 calls/day per IP), and the exact behavior of an unpaid call (returns x402 payment requirements). It omits return format and error handling, keeping it below 5.

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 tight sentences with purpose front-loaded, followed by pricing and sample pointer. Every sentence earns its place, though the payment clause is dense with parenthetical detail.

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?

Covers purpose and payment behavior well, but with no output schema and no annotations it should say more about what a 'candidate' contains and how addresses are normalized. An agent knows how to pay but not what the result looks like.

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 direccion, limit, and provinciaId. The description adds only payment-context information relevant to payment_signature, which is the baseline 3 for a fully documented schema.

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

Purpose4/5

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

States the resource (Argentine address candidates) and the data source (Georef), so an agent can tell what it returns. The verb is implicit rather than explicit, and there is no differentiation from sibling tools, but the domain is unambiguous.

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 pricing and the free sample pointer but gives no when-to-use guidance, no prerequisites, and no alternatives to compare against. 'Free sample: textokit_sample' is a routing hint, not a usage condition.

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.