Skip to main content
Glama
Sign In
fin-advisor

fin-advisor

by TTNAN
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

get_quote

Read-onlyIdempotent

Retrieve non-real-time daily closing prices, percentage changes, and 52-week highs/lows for a ticker to support US equity market analysis and portfolio review.

Instructions

查询最新日线收盘价、涨跌幅、52 周高低点（非实时）。ticker: NVDA/MSFT/AAPL/TSLA/AMZN/QQQ

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

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already establish read-only, idempotent, non-destructive, open-world behavior, so the description doesn't need to restate safety. What it adds beyond annotations is the freshness caveat (非实时) and the field set returned, which is genuinely useful. It does not mention rate limits, data source, symbol coverage limits, or error behavior for unknown tickers.

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?

Two compact clauses: first the returned fields, then the ticker examples. Every phrase is load-bearing, with no filler or repetition. It could be marginally better structured by separating the parameter example from the field list.

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?

With an output schema present, the description doesn't need to explain return formatting, and annotations cover safety. The freshness caveat and example tickers cover the essentials for a single-parameter read tool. Missing is any guidance on symbol scoping or how this differs from get_price_history, which would matter for a tool sitting next to a history sibling.

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 coverage is 0%, so the description must carry the parameter burden, and it partially does by giving example ticker values (NVDA/MSFT/AAPL/TSLA/AMZN/QQQ). However, it doesn't state the expected format precisely (case sensitivity, whether exchange suffixes are allowed) or what happens with unsupported symbols, leaving a real gap at 0% coverage.

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 resource (行情快照) and enumerates the fields returned: latest daily close, change percentage, and 52-week high/low. It also flags that data is non-real-time (非实时), which is a meaningful distinction from a price-history sibling. It stops short of explicitly contrasting with get_price_history, so it doesn't quite earn a 5.

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 when-to-use or when-not-to-use guidance is given. The 'non-real-time' note implies it should not be used for live quotes, but the description never says to prefer get_price_history for time series or other siblings for news/filings. The agent is left to infer selection from sibling names alone.

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