Skip to main content
Glama
cvm-mcp
by msperlin

search_dfp_notes

Read-only

Search the full extracted text of Brazilian CVM annual or quarterly filings to return page-linked snippets, including note numbers when available, so relevant disclosures are not missed.

Instructions

Search the extracted text of the filing, returning snippets with pages.

Searches every page (not only the detected notes) so a hit is never lost to a segmentation failure. Each match carries the PDF page and, when known, the number of the note it belongs to.

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": {
      "term": "<term>",
      "cvm_codes": "<cvm_codes>",
      "year": "<year>"
    },
    "name": "search_dfp_notes"
  }
}

Input Schema

NameRequiredDescriptionDefault
termYesText to look for (accent and case insensitive).
yearYesReference year of the filing (YYYY).
limitNoMaximum number of snippets.
contextNoCharacters of context around each hit.
cvm_codesYesCVM codes to search (see search_company).
data_typeNo'dfp' = annual, 'itr' = quarterly.dfp

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.2.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the description's job is additive, and it is: it explains that every page is searched rather than only detected notes, so a hit is never lost to a segmentation failure, and that matches carry a PDF page plus note number when known. That is genuine behavioral context about recall guarantees and result shape that the annotations do not convey.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The action and return are front-loaded in the first sentence, followed by a short justification of the page-wide search strategy. Three sentences with no filler, though the parenthetical about segmentation failure is slightly verbose for the information it carries.

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 return values need not be described, and annotations cover the safety profile. With six parameters fully documented in the schema, the remaining need is only behavioral context, which the page-wide search note provides; a brief pointer to a sibling for note-scoped retrieval is the only real gap.

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%, so term, year, limit, context, cvm_codes and data_type are all documented in the schema itself. The description adds nothing about parameter semantics beyond that, so the baseline 3 applies.

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 and resource: "Search the extracted text of the filing, returning snippets with pages." That is enough to separate it from retrieval-style siblings like get_dfp_notes and get_dfp_document, though the description never names an alternative explicitly.

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 implied rather than stated: you use it to find terms inside a filing's text. There is no explicit when-to-use versus get_dfp_notes or get_dfp_document, and no prerequisites such as needing a CVM code first beyond the passing parenthetical reference in the schema.

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