Skip to main content
Glama
Sign In
stock-analyzer-mcp

stock-analyzer-mcp

by kevinlin49361128-stack
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

get_macro_snapshot

Read-onlyIdempotent

Retrieves US macroeconomic snapshot from FRED including Treasury yields, Fed Funds, CPI, unemployment, USD index, and VIX to assess macro environment and risk-on/off shifts.

Instructions

取得美國總體經濟快照（FRED 資料）：10 年期公債殖利率、Fed Funds、CPI YoY、失業率、美元指數、VIX。用於判讀總經環境、跨資產情境、Risk-on/off 切換

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_macro_snapshot"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.1

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and idempotentHint=true, establishing safety. The description adds context by specifying the data source (FRED) and the exact indicators returned, which is valuable beyond the annotations.

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, well-structured sentence that front-loads the action and lists indicators efficiently. Every word adds value, with no redundancy.

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 no-parameter, read-only tool, the description adequately covers the output (specific indicators) and purpose. It lacks details on time range or update frequency, but given low complexity, it is sufficiently complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has zero parameters, so baseline is 4. The description fully compensates by detailing what the snapshot contains, making the tool's behavior clear without needing parameter documentation.

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 clearly defines the tool's purpose: getting a US macroeconomic snapshot from FRED, listing specific indicators (10-year yield, Fed Funds, CPI YoY, unemployment, USD index, VIX). This distinctly differentiates it from sibling tools like get_macro_employment or get_macro_inflation.

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?

The description implies usage for interpreting macro environment and risk-on/off switching, but does not explicitly state when to use this tool versus alternatives like get_macro_employment or get_macro_series. Lack of exclusions or when-not-to-use guidance makes it adequate but not exemplary.

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