Skip to main content
Glama
wshobson

MaverickMCP

portfolio_clear_portfolio

Clears all stock positions from a specified portfolio. Confirmation is required to avoid accidental loss.

Instructions

Clear all positions from your portfolio.

CAUTION: This removes all positions from the specified portfolio. This action cannot be undone.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
user_idNoUser identifier (defaults to "default")default
portfolio_nameNoPortfolio name (defaults to "My Portfolio")My Portfolio
confirmNoMust be True to confirm deletion (safety check)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior4/5

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

Without annotations, the description discloses the destructive nature and irreversibility ('This action cannot be undone'). It adds context about removing all positions from the specified portfolio, though it does not mention the confirm parameter requirement.

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?

Two sentences with efficient wording and a clear caution format. No wasted words.

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?

The description covers the core action and warning. It omits the requirement for the confirm flag, but the output schema exists and the tool is simple. A minor 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 coverage is 100% and the parameters are fully described in the schema. The description adds no extra meaning beyond what the schema provides, so baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states 'Clear all positions from your portfolio,' which is a specific verb (clear) and resource (positions in portfolio). It distinguishes from siblings like remove_portfolio_position which likely removes a single position.

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?

The description implies usage for clearing all positions with a caution about irreversibility, but does not explicitly provide when-to-use or when-not-to-use guidance or mention alternative tools.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/wshobson/maverick-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server