BR Intelligence

generate_pix_code

Generate a static PIX copia-e-cola (BR Code) from a PIX key (CPF, CNPJ, phone with +55, e-mail or random key), with optional amount in BRL, receiver name, city, reference and message, following the Central Bank of Brazil standard. Self-checked; nothing is stored. Price: $0.005.

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": {
      "key": "<key>"
    },
    "name": "generate_pix_code"
  }
}

Input Schema

Name	Required	Description
`key`	Yes	PIX key: CPF, CNPJ, phone with +55, e-mail or random key (EVP).
`city`	No	Receiver city, up to 15 characters.
`name`	No	Receiver name, up to 25 characters.
`txid`	No	Reference, letters and digits, up to 25.
`amount`	No	Amount in BRL, up to 2 decimals (e.g. 25.00).
`description`	No	Message shown to the payer.

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 25, 2026

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 behavioral burden and discloses that the result is self-checked, nothing is stored, and the price is $0.005. These are useful non-obvious traits for a generation tool. It does not describe error handling or rate limits, but the key behavioral context is present.

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?

A single, front-loaded sentence with zero wasted words. It packs the resource, input types, optional fields, standard, self-check note, storage behavior, and price into a compact structure.

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 simple generation tool with no output schema, the description explains what is produced (BR Code), that it is self-checked, and that nothing is stored. It could say more about the return value format or error conditions, but an agent has enough to invoke it correctly.

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 six parameters are already documented in the schema. The description mentions the key types and optional amount, receiver name, city, reference, and message, but adds no syntax or constraints beyond the schema. Baseline 3 is appropriate.

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: generate a static PIX copia-e-cola (BR Code) from a PIX key. It clearly distinguishes this generation tool from the sibling decode_pix by naming the output format and source input. An agent can identify the tool's exact function without opening the schema.

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?

The description gives clear context for use: converting a PIX key into a BR Code, with optional amount, receiver details, reference, and message. It does not explicitly name alternatives or when not to use it, but the purpose is sufficiently unambiguous for correct selection.

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

All BR Intelligence tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?