Skip to main content
Glama
Sign In

Equibles

by io.github.daniel3303
OverviewDiscussionsAdmin

Stock Splits

GetStockSplits
Read-only

Get the captured stock splits and reverse splits of an exact stock or ETF listing, newest effective date first, and whether its stored daily prices are confirmed restated onto the post-split share basis across each. A restated split needs no further adjustment of GetStockPrices bars; an unconfirmed one (always so for a listing outside the US) is a break in the price and volume series, never to be restated from the ratio alone. Announced splits can appear before their effective date. Each listing reports its own splits: a share class never inherits another listing's.

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": {
      "ticker": "<ticker>"
    },
    "name": "GetStockSplits"
  }
}

Input Schema

NameRequiredDescriptionDefault
offsetNoNumber of newest matching splits to skip for pagination (default: 0).
tickerYesListed stock or ETF ticker (e.g., NVDA, BRK-B); a listing on another exchange is MIC:TICKER (XAMS:ASML).
endDateNoOptional latest effective date in YYYY-MM-DD format.
startDateNoOptional earliest effective date in YYYY-MM-DD format.
maxResultsNoMaximum number of splits to return (default: 20, max: 500).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior5/5

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

Annotations already cover the safe-read profile, and the description adds genuinely non-obvious behavior: splits are broken per listing, a share class never inherits another listing's splits, non-US listings are always unconfirmed, and announced splits can appear before their effective date. These are exactly the traits an agent could not infer from annotations or schema.

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?

Four sentences, front-loaded with the core purpose and each sentence carrying distinct information about restatement behavior. The prose is dense and clause-heavy, which slows parsing slightly, but nothing is redundant filler.

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?

With no output schema, the description does the work of explaining the critical return attribute (confirmed-restated vs unconfirmed) and the ordering of results. It doesn't enumerate the other fields of a split record (ratio, dates), but the essential interpretation guidance for a read-only listing tool is present.

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 offset, ticker, startDate, endDate, and maxResults are already documented in the schema. The description reinforces date semantics ('newest effective date first') which explains pagination order, but adds no syntax or edge-case detail beyond that. Baseline 3 is appropriate.

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 and resource (get captured stock splits and reverse splits) plus scope (an exact stock or ETF listing), ordering (newest effective date first), and the extra payload (restatement confirmation). It also pre-empts confusion with the price tool by noting the listing-level granularity, so an agent can tell what this returns without opening the schema.

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?

Provides clear operating context: restated splits require no further adjustment of GetStockPrices bars, while unconfirmed ones are a genuine series break and must not be derived from the ratio. That effectively tells the agent when this data matters and how to combine it, though it never states an explicit 'call this when…' trigger or exclusion against the many sibling ownership/price tools.

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

All Equibles toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources