Skip to main content
Glama
Signal8 MCP Server

Signal8 MCP Server

Official

Get Market Metrics

get_market_metrics
Read-only

Retrieve computed stock metrics for a ticker—volume averages, volatility, moving averages, and trend direction—to enable deeper analysis beyond a basic quote.

Instructions

Get computed market metrics for a company: volume averages, volatility, simple moving averages and trend direction, beyond the basic quote.

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

Input Schema

NameRequiredDescriptionDefault
tickerYesStock ticker symbol (e.g., "AAPL", "TSLA")

Output Schema

NameRequiredDescriptionDefault
dataNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered by structured data. The description's only added behavioral content is implying the metrics are precomputed server-side rather than user-configurable. It does not disclose the default lookback windows used for the averages and volatility, or data freshness, which are meaningful for interpreting these numbers.

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?

One sentence, front-loaded with the verb and resource, followed by a compact enumeration of outputs and a differentiator. No filler or redundant restatement of the title.

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?

Output schema exists, so return-value structure need not be explained, and with one required parameter the call surface is simple. However, a metrics tool's usefulness depends on period/lookback assumptions, and the description never states what windows the volume averages, volatility, and SMAs default to, leaving the agent unable to interpret or caveat the numbers.

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?

There is a single parameter with 100% schema description coverage, including format examples ('AAPL', 'TSLA'), so the schema carries the full burden. The description adds no constraint on the ticker beyond what the schema states, such as whether non-equity symbols are accepted. Baseline 3 applies when coverage is complete.

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 gives a specific verb ('Get computed') and resource ('market metrics for a company'), then enumerates the exact metric families returned: volume averages, volatility, moving averages, trend direction. The phrase 'beyond the basic quote' explicitly sets it apart from the sibling get_quote, so an agent can distinguish the two without opening either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

'Beyond the basic quote' signals the selection rule against get_quote, including that it is not a substitute for a raw price lookup. What is missing is an explicit statement of when these derived metrics are not appropriate (e.g., when only a current price or historical bars are needed), so the guidance is clear but not exhaustive.

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