Brapi

Crypto

crypto

Read-onlyIdempotent

brapi.dev — crypto price quote for a coin (e.g. 'BTC') in a target currency (default BRL). Returns price, 24h change, market cap, and volume sourced from Brazilian market data.

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": {
      "coin": "BTC",
      "currency": "BRL"
    },
    "name": "crypto"
  }
}

Input Schema

Name	Required	Description	Default
`coin`	Yes
`currency`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedMay 25, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, and non-destructive behavior. The description adds useful context by specifying return fields (price, 24h change, market cap, volume) and the data source (Brazilian market), which goes beyond the annotation hints. No contradiction.

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?

The description is a single, front-loaded sentence that immediately communicates the core purpose. No filler words, every clause adds relevant information.

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 two-parameter quote tool, the description covers purpose, parameters, and output fields. The output schema presumably handles return structure. Minor limitations, such as what 'Brazilian market data' specifically means, are not disclosed, but overall the context is sufficient.

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 description coverage is 0%, so the description must compensate. It explains 'coin' as a crypto ticker (e.g., 'BTC') and 'currency' with a default of BRL. The schema examples add 'USD' as an alternative, providing sufficient clarity for both parameters.

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 action (price quote), resource (crypto coin), and scope (target currency, Brazilian market data). It distinguishes itself from sibling tools like 'currency' and 'quote' by explicitly mentioning crypto and the data source.

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 context is implied from the name and description, but there is no explicit guidance on when to use this tool versus alternatives like 'currency' or 'quote'. No exclusions or alternative tool references are provided.

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

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