Skip to main content
Glama
zenith-sb-mcp

zenith-sb-mcp

technicals

Read-only

Computes latest technical indicator readings for an IDX stock from daily bars—SMA/EMA, RSI, MACD, Bollinger Bands, ATR, and pivot-cluster support/resistance—so you can reason from numbers.

Instructions

Technical indicator readings for an IDX stock, computed from daily bars: SMA/EMA, RSI, MACD, Bollinger Bands, ATR, and support/resistance levels found by pivot clustering. Returns NUMBERS for reasoning — use price_chart when you want the picture. Every reading reported is the latest defined value of its series. Deep history is paged 12 sessions at a time upstream, so a large bars is slow; pagesFetched reports what the query cost.

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": "technicals"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoLatest session, YYYY-MM-DD
barsNoSessions to analyse (default 200). Ignored if `from` is given.
fromNoEarliest session, YYYY-MM-DD
symbolYesIDX ticker, e.g. BBRI

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint=true, destructiveHint=false, openWorldHint=true), so the description's job is added context, and it delivers: values are the latest *defined* value of each series, deep history is paged 12 sessions at a time upstream, and `pagesFetched` reveals query cost. This is meaningful operational behavior an agent could not infer from 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?

Three tightly packed sentences with zero filler: resource and indicator list first, then the alternative-tool rule, then the performance/paging caveat. Every sentence carries distinct, actionable information and the most decision-relevant content is front-loaded.

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

Completeness5/5

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

There is no output schema, but the description pre-empts the key return questions: results are numbers, each reading is the latest defined value, and `pagesFetched` reports cost. Combined with full schema coverage and annotations, an agent has enough to invoke this correctly and interpret latency.

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?

Schema description coverage is 100%, so a 3 is the baseline; the description adds real meaning by tying `bars` to latency and upstream paging cost, which the schema's 'Sessions to analyse' wording does not convey. It does not add format or semantics beyond the schema for `from` and `to`.

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?

States a specific verb and resource ('Technical indicator readings for an IDX stock, computed from daily bars') and enumerates the exact indicator families returned: SMA/EMA, RSI, MACD, Bollinger Bands, ATR, pivot-cluster support/resistance. An agent can immediately distinguish this computed-indicator tool from siblings like quote or chart_series without opening any 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?

Gives a clear selection rule against one sibling: 'use `price_chart` when you want the picture', establishing that this tool is for numeric reasoning rather than visualization. It also warns that a large `bars` is slow. It stops short of covering other plausible alternatives (e.g. chart_series, keystats) or stating explicit when-not conditions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.