Skip to main content
Glama

br_docs_parser

Validate and decode Brazilian boleto, tax/utility slip, barcode, and NF-e access key data with post-2025 due-date rules for reliable payment and document checks.

Instructions

Brazilian FEBRABAN Bank Boleto (47/44), Tax/Utility Slip DARF/FGTS/IPTU (48/44), and NF-e Access Key (44) validator & decoder with post-2025 due date engine ($0.008 USDC via x402 on Base).

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": {
      "code": "<code>"
    },
    "name": "br_docs_parser"
  }
}

Input Schema

NameRequiredDescriptionDefault
codeYesBrazilian payment slip digitable line (47 digits for Bank Boleto, 48 digits for Tax/Utility Slip like DARF/FGTS/IPTU), 44-digit barcode, or 44-digit NF-e access key.
aiSummaryNoGenerate a concise payment/document summary via Cloudflare Workers AI (default: true).
documentTypeNoOptional explicit parser mode (default: auto).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description must carry behavioral disclosure, and it does add real value by stating the cost ($0.008 USDC via x402 on Base), which signals a paid, likely network-bound call requiring payment setup. It also hints at a 'post-2025 due date engine,' implying date recalculation behavior. However, it never describes what the tool returns (validation verdict, decoded fields, computed due date), so a caller cannot anticipate the response shape.

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?

A single front-loaded sentence that leads with the domain and input classes before the pricing detail. It is dense but every clause carries information; the nested parentheticals make it slightly harder to scan than a two-sentence split would.

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 a three-parameter tool with no annotations and no output schema, the description covers inputs and cost but leaves the return contract undefined — an agent cannot tell whether it gets a boolean, decoded fields, or a due-date calculation. The core 'what it does' is complete; the 'what you get back' is not.

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 all three parameters including the enum values and the aiSummary default. The description's format list mirrors the 'code' parameter description rather than extending it, adding no new semantics. Baseline 3 is appropriate when the schema does the heavy lifting.

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?

The description names a specific verb pair ('validator & decoder') and a precise resource set: FEBRABAN Bank Boleto (47/44), DARF/FGTS/IPTU slips (48/44), and NF-e access keys (44). The digit-count mapping makes the accepted input classes unambiguous. It stops short of naming a sibling such as br_nfe_xml_auditor to clarify that this handles access keys rather than XML documents, so it does not reach the 5 bar for sibling differentiation.

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

Usage Guidelines3/5

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

Usage is implied by the enumerated input formats — an agent can infer 'call this when you have a digitable line, barcode, or access key' — but there is no explicit when-to-use, when-not-to-use, or alternative-tool guidance. Nothing routes the agent between this and br_nfe_xml_auditor for NF-e work.

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