big-mcp-b3

comparar_ativos

Compare multiple B3 assets side by side—quotes, price variation, and dividends—by providing 2 to 10 tickers to get a consolidated overview for informed investment decisions.

Instructions

Compara múltiplos ativos lado a lado (cotação, variação, proventos)

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": {
      "tickers": "<tickers>"
    },
    "name": "comparar_ativos"
  }
}

Input Schema

Name	Required	Description	Default
`tickers`	Yes	Lista de tickers para comparar (mínimo 2, máximo 10)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 4, 2026

TDQS

B3.1/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. The tool performs a comparison and likely returns a table/format for multiple assets, but the description doesn't detail what the output contains, what data source is used, or any limitations on comparison granularity or assets that can be mixed.

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?

A single, efficient sentence that is front-loaded with the verb 'Compara' and conveys the full purpose. Zero waste.

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?

For a simple one-parameter tool with no output schema, the description is mostly adequate. However, since no annotations exist, it would benefit from stating what the returned comparison contains or how to interpret results, and it could compare with sibling single-asset tools to guide selection.

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 100% — the single parameter 'tickers' is already documented in the schema as a list with min 2 / max 10 constraints. The description says 'múltiplos ativos' which adds marginal context, but the description doesn't add semantics beyond what the schema already specifies for the one parameter.

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?

The description states a clear action — compares multiple assets side by side — with specific aspects (cotação, variação, proventos). It distinguishes the tool as a multi-asset comparison tool versus siblings like cotacao_ativo or proventos_ativo which handle single assets.

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 explicit when-to-use or when-not-to-use guidance is provided. The description implies single vs multi-asset use case by nature of the tool, but doesn't name alternatives (e.g., use cotacao_ativo for a single asset). A distinction from sibling tools that serve similar single-asset purposes is implicit only.

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

Deploy Server