Skip to main content
Glama
stockbit-mcp

stockbit-mcp

Seasonality years

price_seasonality_years
Read-onlyIdempotent

Returns the years of seasonality data available for a given stock symbol, so you can check which historical years to query before analyzing recurring price patterns.

Instructions

Which years of seasonality data exist for one symbol.

Returns (Stockbit's data field): data[{desc, value}] — rendered as ' Years'.

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

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

Input Schema

NameRequiredDescriptionDefault
symbolYessymbol

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 readOnlyHint, idempotentHint, and destructiveHint=false, so safety is covered. The description adds real value beyond that by disclosing the return payload shape (data[{desc, value}] rendered as '<desc> Years') and the underlying endpoint, which is important since no output schema exists.

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?

The definition is short and front-loaded: purpose first, then return shape, then endpoint. The 'Returns (Stockbit's data field)' phrasing and the '<desc> Years' rendering hint are slightly cryptic, but nothing is wasted.

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 one-parameter read tool with no output schema, the description supplies the two things that matter most: what it returns and that it is a coverage check rather than data retrieval. Only the relationship to price_seasonality could be spelled out more explicitly.

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 required parameter, and schema coverage is 100% (albeit with a placeholder 'symbol' description). The prose adds no format, exchange, or ticker-convention detail beyond the schema, 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?

The first sentence states a specific verb and resource: it enumerates which years of seasonality data exist for one symbol, which is clearly a metadata/coverage lookup rather than the data itself. This distinguishes it from the sibling price_seasonality without naming it explicitly, leaving a small gap in routing certainty.

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?

Usage is only implied by the phrase 'which years ... exist', suggesting a discovery call before fetching seasonality data. There is no explicit statement of when to prefer it over price_seasonality, no prerequisites, and no mention of what to do with the returned years.

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