Brazil Cvm Financials

Br Financials Search

br_financials_search

Read-onlyIdempotent

Search Brazilian listed companies in the CVM annual-statements data by name (every word must appear; accents ignored), returning cnpj, name, CVM code and the fiscal years available. Use it to find the cnpj to pass to br_financials or br_financial_series. A query matching nothing returns found:false with data_as_of, never an empty list.

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": {
      "name": "petrobras"
    },
    "name": "br_financials_search"
  }
}

Input Schema

Name	Required	Description	Default
`name`	Yes	Company name or part of it, e.g. "vale", "banco do brasil".
`limit`	No	Max companies, 1-100 (default 25).

Output Schema

Name	Required	Description	Default
`found`	No
`source`	No
`licence`	No
`returned`	No
`companies`	No
`truncated`	No
`data_as_of`	No
`fiscal_years_loaded`	No
`latest_filing_received`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 25, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Annotations already declare read-only, idempotent, non-destructive, open-world behavior, but the description adds important semantics beyond that: every word in the query must appear, accents are ignored, and a failed match returns found:false with data_as_of instead of an empty list. Those are non-obvious behavioral traits that materially affect how an agent should interpret results.

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 compact and front-loaded: search behavior first, downstream use second, no-match behavior last. Every sentence adds actionable information with no filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-parameter search tool with full schema coverage, an output schema, and read-only annotations, the description is complete. It covers matching semantics, returned fields, intended downstream use, and the unusual no-match response shape.

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 coverage is 100%, so the schema already documents both parameters. The description still adds meaning beyond the schema for the name parameter by explaining whole-word matching and accent-insensitive matching, though it does not add anything for limit.

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 states a specific verb and resource: search Brazilian listed companies in CVM annual-statements data by name. It also names the downstream tools br_financials and br_financial_series, so an agent can distinguish this lookup tool from the financial-data tools without inspecting schemas.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It explicitly says to use this tool to find the cnpj to pass to br_financials or br_financial_series, which is exactly the routing decision an agent needs. The matching behavior and no-match response are also described, leaving little ambiguity about when and how to invoke it.

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

All Brazil Cvm Financials 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.