Skip to main content
Glama
Sign In
MaverickMCP

MaverickMCP

by wshobson
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

get_user_portfolio_summary

Retrieve a basic summary of your stock portfolio and explore analysis features with sample data.

Instructions

Get basic portfolio summary and stock analysis capabilities.

Returns available features and sample stock data.

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_user_portfolio_summary"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/5.0
Behavior2/5

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

No annotations provided, so description must disclose behavior. Only states 'Returns available features and sample stock data' – no mention of read-only nature, side effects, authentication, or data scope.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, short, but the first sentence is unclear and combines two ideas. Could be more direct and front-loaded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With an output schema present, the description need not detail return format, but it fails to explain what 'available features' means or how the tool fits into a workflow. Incomplete for a capabilities summary 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?

No parameters defined; baseline is 4 for zero-parameter tools. Description adds no parameter info, but none is needed.

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

Purpose3/5

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

Description states 'Get basic portfolio summary and stock analysis capabilities' which is a verb+resource, but the phrase 'stock analysis capabilities' is vague and does not clearly differentiate from many sibling tools like get_my_portfolio, portfolio_get_my_portfolio, or capabilities discovery tools.

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 alternatives. Does not mention prerequisites, when-not-to-use, or suggest other tools for more specific portfolio data.

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