Skip to main content
Glama
Sign In
yfinance

yfinance

by ozp
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get_stock_info

Retrieve comprehensive stock information and metadata for any ticker symbol, including financial data, company details, and more.

Instructions

Get comprehensive stock information and metadata.

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": {
      "symbol": "<symbol>"
    },
    "name": "get_stock_info"
  }
}

Input Schema

NameRequiredDescriptionDefault
symbolYesStock ticker symbol.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.4

TDQS

C2.5/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 for behavioral disclosure. The description only mentions fetching information, which implies a read operation, but does not discuss data freshness, rate limits, or any side effects. This is insufficient for a tool returning 'comprehensive' data.

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?

The description is a single sentence with no waste, but it is overly terse, omitting important details that would justify its length. It is concise but at the expense of clarity and completeness.

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?

Given the tool's broad name and lack of output schema, the description fails to specify what 'comprehensive' includes (e.g., price, fundamentals, metadata). With numerous sibling tools providing specific data, the description should clarify the scope but does not, leaving the agent uncertain about the tool's coverage.

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 single parameter 'symbol' has a schema description of 'Stock ticker symbol.', which is adequate but minimal. The tool description does not add additional meaning beyond the schema (e.g., format requirements, case sensitivity). With 100% schema coverage, the baseline score is 3.

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?

The description states it provides 'comprehensive stock information and metadata', which indicates a broad overview. However, 'comprehensive' is vague and does not specify what exactly is included, nor does it differentiate from the many sibling tools that offer specific stock data.

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 is provided on when to use this tool versus the extensive list of sibling tools (e.g., get_current_stock_price, get_balance_sheet). The agent is left to infer that this tool aggregates general info, but no explicit when-to-use or when-not-to-use advice is given.

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