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

stock-analyzer-mcp

by kevinlin49361128-stack
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

get_fed_policy_stance

Read-onlyIdempotent

Determines the Federal Reserve's current monetary policy stance and six-month trend using effective federal funds rate data from FRED.

Instructions

判讀 Fed 當前貨幣政策立場（緊縮/中性/寬鬆）與近 6 個月趨勢（升息/持平/降息），基於 FRED 的 DFF（聯邦基金有效利率）

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.1

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true. The description adds the data source (FRED DFF), but does not disclose methodology, data freshness, or error handling. Adequate but not rich.

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?

Single sentence clearly stating purpose and data source. No wasted words; front-loaded and efficient.

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 read-only tool with no parameters and annotations present, the description is fairly complete. It explains the tool's output and basis. Could mention output format, but overall adequate.

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?

No parameters exist; schema coverage is trivially 100%. The description does not need to add parameter info. Baseline for 0 params is 4, and no additional value is required.

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 states the tool interprets Fed's monetary policy stance (tight/neutral/loose) and 6-month trend based on FRED's DFF rate. The verb '判讀' (interpret) and specific resource differentiate it from sibling tools like get_macro_series.

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 explicit guidance on when to use this tool versus alternatives. The description implies it is for derived analysis of Fed policy, but does not mention exclusions or when to choose other macro tools.

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