Skip to main content
Glama
Sign In
garu-mcp

garu-mcp

Official
by Garu-Pagamentos
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

create_boleto_charge

Create a boleto bancario charge with customer and product details, returning the bank slip line for payment.

Instructions

Create a boleto bancario charge. Returns a bank slip line for payment.

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": {
      "productId": "<productId>",
      "customer": "<customer>"
    },
    "name": "create_boleto_charge"
  }
}

Input Schema

NameRequiredDescriptionDefault
customerYes
productIdYesProduct UUID
additionalInfoNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.18.0

TDQS

B3.3/5.0
Behavior2/5

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

No annotations are provided, so the description bears full responsibility. It states that a bank slip line is returned but fails to disclose whether the charge is immediately created, how payment confirmation works, authentication needs, or error scenarios. For a creation tool, these gaps are significant.

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?

The description is very concise at two sentences. However, it omits important context about parameters and behavior, making it less valuable than it could be while still being brief.

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?

With no output schema and minimal annotations, the description provides only the barest outline. It explains the return value but not how to use the return or handle errors. For a tool with 3 parameters and a nested object, completeness is lacking.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is only 33%, and the description adds no parameter guidance beyond what the schema provides. Many fields in the nested customer object lack descriptions, and the tool's purpose does not explain how parameters like productId or additionalInfo affect the charge.

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?

The description clearly identifies the tool as creating a boleto bancario charge and distinguishes it from siblings like create_pix_charge or scheduled charge operations. The verb 'create' and resource 'boleto bancario charge' are specific.

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?

No explicit guidance on when to use this tool versus alternatives. While the name and description imply it's for boleto payments, there is no mention of prerequisites, exclusions, or comparison to similar tools like create_pix_charge or scheduled charges.

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

Deploy Server

Other Tools