Skip to main content
Glama

stocks_get_quote

Fetch current stock prices and market data to evaluate investment opportunities.

Instructions

Get current stock price and market data

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • server.js:81-81 (registration)
    Tool 'stocks_get_quote' is registered in the TOOLS array as ['stocks_get_quote', 'Get current stock price and market data'].
    ["stocks_get_quote", "Get current stock price and market data"],
  • server.js:106-110 (registration)
    The tool registration loop: for each entry in TOOLS, server.tool() is called with the name and description, and an empty schema object. The handler is a stub that returns an inspection message.
    for (const [name, desc] of TOOLS) {
      server.tool(name, desc, {}, async () => ({
        content: [{ type: "text", text: "This is an inspection stub. Install Local MCP: npx -y local-mcp@latest setup" }],
      }));
    }
Behavior2/5

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

No annotations are provided, so the description bears full burden. It only states the basic function without disclosing behavioral traits such as authentication requirements, rate limits, data freshness, or whether it uses current context. For a tool with no parameters, this leaves the agent uncertain about how it operates.

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, front-loaded sentence that conveys the core function without unnecessary words. It is efficient and easy to parse.

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 no parameters and no output schema, the description is minimal. It does not specify what constitutes 'market data' (e.g., open, high, low, volume) or how the stock is identified. While a simple tool may not need extensive detail, the lack of clarification on how it derives the stock symbol leaves a gap.

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?

Input schema has zero parameters, so schema description coverage is 100%. The description does not add any parameter meaning, but it also fails to explain why there are no parameters (e.g., implicit stock symbol via context). According to guidelines, 0 params = baseline 4, but the lack of clarity reduces the score to 3.

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 'Get current stock price and market data' clearly states the action and resource. It distinguishes from sibling tools like stocks_get_chart (historical data) and stocks_search_symbol (search). However, it does not explain how the stock symbol is determined given the input schema has no parameters.

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, nor any prerequisites or constraints. The description lacks context on when to invoke stocks_get_quote instead of stocks_get_chart or stocks_search_symbol.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/lanchuske/local-mcp-releases'

If you have feedback or need assistance with the MCP directory API, please join our Discord server