Skip to main content
Glama

FinanceQuery

Stock Split History

get_splits
Read-onlyIdempotent

Get historical stock split history for a 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>",
      "range": "<range>"
    },
    "name": "get_splits"
  }
}

Input Schema

NameRequiredDescriptionDefault
rangeYesTime range: 1y|2y|5y|10y|max (default: max)
fieldsNoComma-separated list of GraphQL field names to include; omitted = curated default set
symbolYesStock ticker symbol

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true and destructiveHint=false, so the safety profile is fully covered elsewhere. The description adds no behavioral context beyond the title—nothing about data source, coverage period, or whether split ratios/adjustment factors are included.

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?

A single front-loaded sentence with no filler or repetition. It is efficient, though its brevity borders on under-specification rather than optimal density.

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

Completeness3/5

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

For a simple read-only tool with a fully documented three-parameter schema and complete annotations, this is minimally sufficient. It omits sibling disambiguation and any note on output shape, which would help an agent choose correctly among many get_* data tools.

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 the schema already explains symbol, range (with enum-like values and a default), and fields. The description adds no meaning beyond the schema, which is the expected baseline for fully documented parameters.

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 gives a specific verb ('Get') and resource ('historical stock split history') scoped to a symbol, so an agent can tell what data comes back. It does not differentiate itself from adjacent siblings such as get_dividends, leaving a small ambiguity for corporate-action queries.

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

Usage Guidelines2/5

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

There is no guidance on when to use this versus alternatives (e.g. get_dividends for cash distributions) and no stated prerequisites or exclusions. The only implied usage is 'when you need split history for a ticker'.

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.