Skip to main content
Glama
Sign In
FinPilot AI

FinPilot AI

by ShahzaadAhmed
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

get_stock_price

Retrieve real-time stock prices and historical data for any ticker, with customizable periods from one day to one year.

Instructions

Retrieve the current real-time stock price and historical data for a given ticker symbol.

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

Input Schema

NameRequiredDescriptionDefault
periodNoThe historical time period to fetch1D
tickerYesThe stock ticker symbol (e.g., AAPL, MSFT)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.7/5.0
Behavior3/5

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

No annotations are provided, so the description must convey behavioral traits. The verb 'retrieve' implies a read-only operation, but it doesn't disclose data freshness, return format, or any rate limits. It adds some context about real-time and historical data but remains 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?

The description is a single, clear sentence that immediately states the action and scope. No filler or redundant information.

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?

Given the simple tool with two parameters and no output schema, the description covers the core purpose but omits mention of the period parameter and the exact return data. This leaves some ambiguity about what 'historical data' includes, making it slightly incomplete.

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 schema already documents both parameters (ticker and period) with descriptions and an enum for period, achieving 100% coverage. The description adds no additional meaning beyond mentioning the ticker symbol, so it relies fully on the schema.

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 uses a specific verb 'retrieve' and names the resource 'current real-time stock price and historical data' along with the input 'ticker symbol', clearly distinguishing it from sibling tools like get_market_news or get_risk_assessment.

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 when-to-use or alternatives are given; usage is implied by the description. It doesn't contrast with get_financial_statements or run_dcf_valuation, leaving the agent to infer when to select this tool.

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