Skip to main content
Glama

textokit_cuit_ar

Validate Argentine CUIT or CUIL tax id (check digit, KYC onboarding). 0.001 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": {
      "identifier": "<identifier>"
    },
    "name": "textokit_cuit_ar"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeNoOptional caller-declared type: auto, CUIT or CUIL. Defaults…
identifierYesEleven digits or XX-XXXXXXXX-X format, supplied as text; up…
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 / identifier / description
      Previous value: -"Eleven digits or XX-XXXXXXXX-X format, supplied as text; up to 32 characters."New value: +"Eleven digits or XX-XXXXXXXX-X format, supplied as text; up…"
    • 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 / type / description
      Previous value: -"Optional caller-declared type: auto, CUIT or CUIL. Defaults to auto; does not confirm the type."New value: +"Optional caller-declared type: auto, CUIT or CUIL. Defaults…"
  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 full burden and does well on the money side: it discloses 0.001 USDC per call on Base, 10 free calls/day per IP, and that an unpaid call returns x402 payment requirements rather than a validation result. It does not describe what a successful response contains (valid/invalid, normalized form, failure reason), which is the remaining gap given there is no output schema.

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?

Three short clauses, front-loaded with the verb and resource, then cost, then the free alternative. Every clause carries distinct information with no repetition.

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?

For a low-complexity validator with fully documented parameters, the definition covers purpose, paid-API mechanics, failure mode, and a free trial path. The one omission — return value shape — matters because no output schema exists, keeping it from a 5.

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% and both 'identifier' formats (11 digits or XX-XXXXXXXX-X) and the 'type' enum are already documented in the schema. The description adds only the notion of check-digit validation and never mentions 'payment_signature', so it does not exceed the schema's information.

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 ('Validate') and resource ('Argentine CUIT or CUIL tax id') and adds the scope detail 'check digit, KYC onboarding'. No sibling tool in the list covers Argentine tax IDs, so the agent can route here without ambiguity.

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 a clear use case (KYC onboarding / check-digit validation) and, notably, routes cost-sensitive callers to an alternative by naming 'textokit_sample' as a free sample. It lacks an explicit 'when not to use this' statement, so it stops short of a 5.

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.