Skip to main content
Glama
Sign In
trading-mcp-server

trading-mcp-server

by mukul8896
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

calculate_ema

Compute the latest exponential moving average for a given stock symbol, period, and timeframe to analyze market trends.

Instructions

Exponential moving average (latest value).

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": {
      "symbol": "<symbol>"
    },
    "name": "calculate_ema"
  }
}

Input Schema

NameRequiredDescriptionDefault
symbolYes
periodNo
timeframeNoONE_DAY

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.4/5.0
Behavior2/5

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

With no annotations, the description carries full burden. It only states it computes EMA and returns the latest value, but lacks details on price basis, calculation method, or any side effects. This is insufficient for safe use.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single sentence, which is concise but at the expense of necessary detail. It is front-loaded with the core purpose but lacks structure for additional context.

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

Completeness1/5

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

Given no output schema, no annotations, and 0% schema description coverage, the description fails to explain output format, parameter effects, or how the tool fits among many sibling technical indicators. It is severely incomplete.

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

Parameters1/5

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

The schema has 0% description coverage and the tool description does not explain any parameter. Agents must infer meanings from names and types alone, which is inadequate for correct usage.

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 specifies the tool calculates an exponential moving average and returns the latest value, distinguishing it from SMA and other indicators. However, it does not differentiate from tools like MACD which also involve EMAs, and the phrasing is minimal.

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 guidance is provided on when to use this tool versus alternatives (e.g., SMA, MACD). There are no prerequisites or context about suitability for trends.

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