Skip to main content
Glama
cvm-mcp
by msperlin

get_dfp_document

Read-only

Retrieve filing metadata and the download link for a complete CVM annual or quarterly document by company codes and reference year, including the ZIP with statement XML, notes PDF, and company data.

Instructions

Filing metadata and the download link of the full document.

The link points to the CVM ZIP with the complete filing: an XML with the statement numbers, a PDF with the notas explicativas and the company data. Use get_dfp_notes to read the notes without handling the file yourself.

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

Input Schema

NameRequiredDescriptionDefault
yearYesReference year of the filing (YYYY).
cvm_codesYesCVM codes (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.9/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 safety profile is covered. The description adds real context beyond them: the returned link is a ZIP archive whose internal structure (XML + PDF) is spelled out, telling the agent it will have to handle a file rather than get parsed values. It does not mention archive size, link expiry, or how multiple CVM codes are packed.

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?

Three short sentences, front-loaded with what the tool returns before detailing archive contents and the sibling alternative. The middle sentence listing XML and PDF components is dense but earns its place by setting expectations about the payload. Minor trailing whitespace/noise aside, there is little waste.

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-value documentation is not required, and the description still characterizes the return as a file link. For a read-only lookup with fully documented parameters this is nearly complete; only the multi-company behavior of cvm_codes is left unaddressed.

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% and all three parameters (year, cvm_codes, data_type) are documented in the schema, so the baseline is 3. The description adds nothing about parameter behavior, such as whether the maxItems=20 cvm_codes list returns one archive per company or a combined download.

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 names the specific resource: filing metadata plus a download link to the full CVM ZIP filing, and enumerates what the ZIP contains (XML with statement numbers, PDF with notas explicativas and company data). It is clearly distinguishable from get_dfp_notes, which is named as the read-in-place alternative. It lacks an explicit verb like 'retrieve' but the resource and payload are unambiguous.

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

Usage Guidelines4/5

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

It gives a concrete routing rule: use get_dfp_notes when you want to read the notes 'without handling the file yourself', implying this tool is for when you need the raw document. It does not cover when to prefer get_financial_statements or get_statement_summary, but the guidance against the closest sibling is explicit.

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