Skip to main content
Glama
Sign In

Brapi

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Brapi Currency

brapi_currency
Read-onlyIdempotent

brapi.dev — currency conversion rate for a pair (e.g. 'USD-BRL'): current bid/ask rate and daily change. Covers major pairs against BRL and other currencies.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "currency": "USD"
    },
    "name": "brapi_currency"
  }
}

Input Schema

NameRequiredDescriptionDefault
currencyYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds the currency-pair scope ('against BRL and other currencies'), but says nothing about authentication/API-key needs, rate limits, or freshness of the quoted rate — relevant for an external market-data endpoint.

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?

Two compact sentences, front-loaded with the resource and its output shape, with no filler. The scope clause about BRL pairs earns its place by bounding coverage.

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?

An output schema exists, so the return-value mention is partly redundant but harmless, and the tool is low-complexity with a single required parameter. The main missing piece is auth/access context and resolving the single-code vs pair-format question.

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 0%, so the description must carry the burden: it does supply a format hint ('USD-BRL'), which is genuinely useful. However, that pair format conflicts with the schema's own examples of a single code ('currency':'USD', 'currency':'EUR'), leaving the agent unsure whether to pass 'USD' or 'USD-BRL' — a real ambiguity risk.

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?

States a specific verb+resource ('currency conversion rate for a pair') plus the returned fields (bid/ask rate, daily change) and the domain ('pairs against BRL and other currencies'). This clearly separates it from quote-oriented siblings like brapi_quote and brapi_inflation, though it never names an alternative directly.

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 only implied by the resource name — an agent can infer it is for FX rates, but there is no explicit when-to-use, when-not-to-use, or pointer to a sibling such as brapi_quote for equities. No prerequisites or constraints are stated.

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

All Brapi toolsInspect
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