dlp-invest-mcp

Overview Schema Source Related Servers Discussions Admin

obter_operacoes_tool

Retrieve DLPInvest operations filtered by portfolio, status, and date range, with pagination. Returns operation data or an error for reporting.

Instructions

Recupera a lista de operacoes do sistema DLPInvest.

Args:
    carteira: ID ou nome da carteira para filtrar.
    status: Status da operacao (aberta, fechada, pendente).
    data_inicial: Data inicial no formato YYYY-MM-DD.
    data_final: Data final no formato YYYY-MM-DD.
    limite: Maximo de resultados a retornar.
    offset: Paginacao (quantidade de itens a pular).

Returns:
    Dict with ``success`` and either ``data`` or ``error``.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`limite`	No
`offset`	No
`status`	No
`carteira`	No
`data_final`	No
`data_inicial`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 5, 2026

TDQS

B3.4/5.0

Behavior3/5

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

No annotations are provided, so the description carries the burden. It does disclose the return contract ('success' plus 'data' or 'error') and indicates pagination via offset, which is genuine behavioral context. It stops short of stating permissions, result caps, or default behavior beyond the schema defaults.

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?

Uses a clean Args/Returns structure and leads with the purpose sentence before parameters. Well-sized with no filler, though the Args section is somewhat verbose relative to the sparse top-line description.

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?

Six parameters are all documented and the return shape is described even though an output schema exists. With no annotations, the safety profile is unaddressed, but the description is largely sufficient for a filtered-list read tool.

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, and it does: it labels all six parameters, gives accepted status values (aberta, fechada, pendente), specifies the date format (YYYY-MM-DD), and explains offset as items to skip. It could be slightly stronger on how carteira accepts either ID or name semantics.

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 clear verb ('Recupera') and resource ('lista de operacoes do sistema DLPInvest'), so the agent knows what it returns. However, it does not differentiate from close siblings like obter_extrato_tool or obter_posicao_tool, which could plausibly retrieve overlapping transaction data.

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 guidance on when to use this tool versus the many sibling listing tools, and no exclusions or prerequisites. The description merely enumerates filter parameters without saying what scenario selects this tool.

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

Deploy Server