List portfolio positions with optional asset class filter. Get quantity, average and current prices, invested and market values, and unrealized P&L in BRL.
List all positions in the portfolio. Optional filter by asset_class. Returns each position with quantity, avg/current price, invested vs market value, and unrealized P&L. Values in BRL (Brazilian Reais).
| Name | Required | Description | Default |
|---|---|---|---|
| asset_class | No |
Changes observed during successful MCP inspections.
v0.12.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided; the description explains the returned fields but does not mention side effects, costs, or limits. Since this is a read operation, the lack of destructive-behavior warnings is acceptable but still incomplete.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is succinct and well-structured, covering core functionality and return fields without unnecessary verbosity.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The description provides sufficient context for a straightforward listing operation, including the meaning of returned values; minor gaps exist around edge cases but are not critical.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The single parameter asset_class is documented via its enum values but no description is given beyond the filter mention; the schema carries the possible values, and the description adds minimal extra context.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Clearly states the tool lists all positions in the portfolio, with an optional filter by asset class, distinguishing it from related portfolio tools.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
While it describes what the tool does and the optional filter, it does not explicitly contrast with sibling tools like get_portfolio_summary or suggest_buys, though the scope is clear enough.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.