Skip to main content
Glama
Sign In
MaverickMCP

MaverickMCP

by wshobson
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

get_stock_info

Retrieve fundamental stock data including market cap, P/E ratio, sector, and industry for any ticker symbol.

Instructions

Get fundamental data: market cap, P/E ratio, sector, industry, and more.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "ticker": "<ticker>"
    },
    "name": "get_stock_info"
  }
}

Input Schema

NameRequiredDescriptionDefault
tickerYesStock ticker symbol

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries full burden. It only mentions data retrieval and does not disclose potential behaviors like error handling for invalid tickers, rate limits, or whether it's purely read-only. The description is too minimal for a tool with no other behavioral context.

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?

The description is a single sentence of 10 words, highly concise with no filler. It front-loads the purpose. However, it could be slightly expanded to include basic behavioral context without harming conciseness.

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

Completeness3/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 explain return values. The tool is simple (1 required param, no enums), so the description plus schema cover the basics. However, missing usage guidelines and behavioral transparency reduce completeness.

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 description coverage is 100%, with a clear description for the single parameter 'ticker'. The description adds value by hinting at the output specifics (e.g., market cap, P/E ratio), but does not enhance parameter meaning beyond the schema. Baseline 3 is appropriate.

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?

The description clearly states the verb 'Get' and the resource 'fundamental data' with specific examples (market cap, P/E ratio, sector, industry). It distinguishes from other data-fetching tools like data_fetch_stock_data by focusing on fundamental metrics, though it doesn't explicitly differentiate from the sibling 'data_get_stock_info'.

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. The description only states what it does, with no mention of prerequisites, when-not-to-use, or comparisons to similar tools like data_fetch_stock_data or data_get_stock_info.

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