Skip to main content
Glama

The Market Calendar

Seasonality by month

monthly_seasonality
Read-only

Average and median return, share of years up, best and worst year for each calendar month of an asset. Use for 'what's the best month for X', 'is September bad for stocks'.

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": {
      "asset": "<asset>"
    },
    "name": "monthly_seasonality"
  }
}

Input Schema

NameRequiredDescriptionDefault
assetYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already establish readOnlyHint=true and openWorldHint=false, so safety is covered. The description goes beyond that by enumerating the returned statistics (average, median, share of years up, best/worst year), which is valuable since there is no output schema. It omits the historical span of the data, a minor gap.

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?

Two sentences with zero filler: the first front-loads the output content, the second front-loads the usage triggers. Every clause earns its place.

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 tool with no output schema, the description adequately conveys both what is computed and when to call it. The main missing piece is the lookback window / data vintage, which an agent might want when judging results.

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 parameter whose allowed values are fully enumerated in the schema, so the schema does the heavy lifting despite 0% description coverage. The description only says 'of an asset' and adds no meaning (e.g. asset class coverage or granularity) beyond the enum itself.

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 names a specific verb set (average/median return, share of years up, best/worst year) scoped to 'each calendar month of an asset', which tells an agent exactly what the tool computes. It implicitly separates itself from day_seasonality by specifying calendar months, though it does not name that sibling explicitly.

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?

The 'Use for' clause supplies concrete trigger phrasings ('what's the best month for X', 'is September bad for stocks'), which gives clear context for selection. It stops short of stating when NOT to use it or pointing to day_seasonality/window_seasonality as alternatives.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources