Skip to main content
Glama
stockbit-mcp

stockbit-mcp

Seasonality

price_seasonality
Read-onlyIdempotent

Calculate average monthly returns for a symbol across past years to identify seasonal price patterns and support month-based investment analysis.

Instructions

Average monthly return of one symbol over past years (Seasonality tab).

Returns (Stockbit's data field): data{avg{columns[]}, price_change[], up{columns}, down{columns}, total_months{columns}, prob{columns}} (monthly table; column shape not resolved).

Endpoint: GET exodus /company-price-feed/seasonality/{symbol}.

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>",
      "back_year": "<back_year>",
      "year": "<year>"
    },
    "name": "price_seasonality"
  }
}

Input Schema

NameRequiredDescriptionDefault
yearYesCurrent calendar year.
symbolYessymbol
back_yearYesLookback years; value from /seasonality/{symbol}/years (UI picks 10th entry or last).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and open-world, so the safety profile is covered; the description adds the concrete endpoint and, importantly, the shape of the returned data block plus an honest caveat that the column shape is unresolved. That caveat is valuable because it warns the agent not to assume a fixed table layout, though it does not say whether back_year has bounds or how failed symbol lookups behave.

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 one-line purpose, then a compact return-shape block and endpoint, with no filler sentences. The inline data{...} dump is a bit dense but every piece carries information, especially since no output schema exists.

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 three-required-parameter read tool with no output schema, the description compensates well by naming the endpoint and sketching the return structure. The residual gap is the admitted unresolved column shape and the absence of any note on empty results or out-of-range back_year values.

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?

Schema description coverage is 100%, so symbol, year, and back_year are already documented, including the non-obvious hint that back_year comes from the /seasonality/{symbol}/years endpoint. The description adds only the endpoint template and no further semantics, so the baseline of 3 applies.

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?

States a specific computation (average monthly return) on a specific resource (one symbol over past years) and ties it to a named UI surface (Seasonality tab), which lets an agent distinguish it from generic price-history tools. It stops short of naming the closely related price_seasonality_years sibling, which only appears indirectly via a path reference in one parameter description.

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

Usage Guidelines3/5

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

The description implies the use case (analyzing monthly seasonality for a symbol) but never states when to choose this over price_history or price_performance, nor any prerequisites such as having first fetched valid lookback values. Usage context is inferable rather than explicit.

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