Skip to main content
Glama
portfolio-signals-mcp

portfolio-signals-mcp

get_quote

Fetch current stock or ETF quotes by ticker to get price, daily change, volume, and 52-week range for portfolio analysis.

Instructions

Get the current quote for a stock/ETF ticker: price, day change, volume, and 52-week range.

Args: ticker: Symbol like 'AAPL', 'MSFT', 'VOO'.

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

Input Schema

NameRequiredDescriptionDefault
tickerYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does add real value by listing what the response contains since there is no output schema. However, it says nothing about quote freshness (real-time vs delayed), behavior on an invalid or delisted ticker, or whether the call is a pure read with any rate constraints.

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?

One front-loaded sentence covering purpose and return fields, followed by a short Args block. The Args entry partly restates the schema but the examples earn their place; there is no wasted prose.

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

Completeness4/5

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

For a one-parameter lookup with no output schema, the description covers purpose, return shape, and ticker format, which is close to sufficient. The main remaining gap is data-freshness and error behavior, which matters for a quote tool but is a modest omission.

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 0% for the single required parameter, so the description must compensate. It does so reasonably by defining ticker as a symbol with concrete examples ('AAPL', 'MSFT', 'VOO'), clarifying the expected format, though it does not mention exchange prefixes or case sensitivity.

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 names a specific verb and resource ('get the current quote for a stock/ETF ticker') and enumerates the returned fields (price, day change, volume, 52-week range), which inherently separates it from get_technical_signals and compare_tickers. It stops short of explicitly naming those siblings, so differentiation is implied by scope rather than stated.

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?

Usage is only implied: an agent can infer this is the tool for a single-ticker snapshot, but nothing says when to prefer it over compare_tickers or get_technical_signals, and there are no noted prerequisites or exclusions.

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