Skip to main content
Glama
silasrm

mcp-brasilapi

by silasrm

bancos__buscar

Look up a Brazilian bank by its numeric code, such as 1 for Banco do Brasil.

Instructions

Busca um banco a partir do seu código (ex.: 1 = Banco do Brasil).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
codeYesCódigo do banco.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior2/5

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

No annotations are provided, so description carries full burden. It does not disclose behavior on invalid codes, return format, or whether multiple results are possible. Basic operation is stated but lacks important details.

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?

Single sentence, no wasted words, directly conveys the essence of the tool.

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?

Tool is simple with one parameter and an output schema exists, so description need not detail return values. The example aids understanding. Minor gap: no mention of edge cases.

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

Parameters4/5

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

Schema covers the parameter with a description, and the tool description adds a concrete example (code 1 = Banco do Brasil), adding value beyond schema.

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?

Description clearly states the tool searches for a bank by its code, and provides an example. It distinguishes itself from sibling tool bancos__listar (which lists banks).

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?

No guidance on when to use this tool versus alternatives like bancos__listar or other search tools. The agent must infer usage from context.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/silasrm/mcp-brasilapi'

If you have feedback or need assistance with the MCP directory API, please join our Discord server