Skip to main content
Glama
Sign In
MaverickMCP

MaverickMCP

by wshobson
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

get_my_portfolio

Retrieve all portfolio positions with live prices and profit/loss calculations. Track your investment performance with current data.

Instructions

Get all portfolio positions with live P&L calculations.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_my_portfolio"
  }
}

Input Schema

NameRequiredDescriptionDefault
include_current_pricesNoInclude real-time prices and P&L (default True)

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/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 full burden. It mentions 'live P&L calculations', implying real-time data, but does not disclose potential latency, rate limits, or whether it requires authentication. The behavioral detail is minimal.

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?

A single sentence that is direct and efficient. No unnecessary words or padding. It front-loads the key action and object.

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?

Given the tool's low complexity (one optional param, high schema coverage, and an output schema), the description is largely sufficient. It covers the core functionality. The presence of an output schema reduces the need to explain return values. However, with many sibling tools, a bit more context on its specific use case would be beneficial.

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?

The input schema has 100% coverage (one boolean param documented). The description adds 'live P&L calculations', which gives context to the 'include_current_prices' parameter but does not explain the default behavior or what happens when false. Since schema already documents the param, description adds modest value.

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 'Get all portfolio positions with live P&L calculations', using a specific verb and resource. It effectively differentiates from sibling tools like 'add_portfolio_position' and 'remove_portfolio_position' which are for mutation.

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?

No explicit guidance on when to use this tool versus alternatives. While the purpose is clear, there is no mention of context, prerequisites, or exclusions. Among many sibling portfolio tools, this would benefit from stating its scope (e.g., fetching vs. analyzing).

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

Deploy Server

Other Tools