Skip to main content
Glama
zenith-sb-mcp

zenith-sb-mcp

seasonality

Read-only

Retrieve month-by-month seasonal price behavior for one IDX stock across a ten-year lookback in a single request, so you can compare how it performed in each calendar month.

Instructions

Month-by-month seasonal price behaviour for one IDX stock: how it has done in each calendar month across Stockbit's fixed ten-year lookback, in ONE request. year is the END of that lookback, not a number of years — omit it and the current year is sent, because the endpoint rejects the request outright without one. back_year is passed through unchanged. Stockbit's own client sends it and this project has not observed whether it means a start year or a count of years back, so do not read meaning into it; it is accepted so the parameter is reachable, not because its effect is known. PENDING: the response shape is unverified, so nothing is renamed — data is exactly what Stockbit returned. Read the field names out of it rather than assuming any. An empty or null data means Stockbit has no seasonality series for that symbol and year, which is normal for recently listed companies; it is not an error and not a reading of zero. This is a price-history statistic, not a forecast, and it says nothing about why a month was strong.

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

Input Schema

NameRequiredDescriptionDefault
yearNoEnd year of the ten-year lookback (default: current year)
symbolYesIDX ticker, e.g. BBRI
back_yearNoStockbit's back_year parameter, passed through as given

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare readOnly/openWorld/non-destructive, but the description adds substantial behavior beyond them: the lookback is fixed at ten years, `year` is the end of that window, `back_year` is an unverified pass-through, the response shape is PENDING and should be read from the payload rather than assumed, and empty data carries a specific non-error meaning.

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

Conciseness4/5

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

Front-loaded with the core statement, then proceeds parameter by parameter and ends with a scope disclaimer. A few clauses are redundant — 'accepted so the parameter is reachable, not because its effect is known' largely restates the preceding sentence — but overall the density is justified.

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?

With no output schema and an unverified response shape, the description compensates by telling the agent to read field names from `data` and how to interpret empty results. Parameters, edge cases, and interpretive limits are all covered, so nothing an agent needs to call this correctly is missing.

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 coverage is 100%, so the baseline is 3, but the description genuinely adds meaning: it clarifies that `year` is the END of the lookback rather than a count, and that the server rejects calls without it. It also explicitly flags that `back_year`'s semantics are unobserved and should not be interpreted, which goes beyond the schema's 'passed through as given'.

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+resource+scope: 'month-by-month seasonal price behaviour for one IDX stock' across a 'fixed ten-year lookback'. It is unmistakably distinct from any sibling in the list (technicals, chart_series, keystats), none of which claim seasonal per-calendar-month aggregation.

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 clear contextual guidance: omit `year` and the current year is sent because the endpoint rejects the request otherwise, and an empty/null `data` is normal for recently listed companies rather than an error or a zero reading. It does not name an alternative tool for related price-history questions or state exclusions, so it falls short of a 5.

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