Skip to main content
Glama

Index Add/Drop Events

sv_index_events
Read-only

Index membership add/drop events derived from public holdings + wiki sources (index_events panel). Params: ticker, start/end, limit. Free with X-ORKID-API-Key or $0.005 USDC/call via x402.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "sv_index_events"
  }
}

Input Schema

NameRequiredDescriptionDefault
endNoEnd date YYYY-MM-DD
limitNoMax rows, default 100, cap 500
panelNoPanel to query (default first). Available: index_events
startNoStart date YYYY-MM-DD
tickerNoTicker, e.g. "AAPL"

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered; the description adds genuinely new context: the data provenance (public holdings + wiki, implying derived/approximate coverage) and the authentication/payment model (X-ORKID-API-Key or $0.005 USDC via x402). It does not disclose ordering, pagination behavior, or how sparse the derived events may be.

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?

Two short sentences, front-loaded with what the tool returns and followed by access mechanics. The 'Params:' clause is mild duplication of the schema, but nothing is bloated or buried.

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?

With no output schema, the description should say what a returned event row contains (event date, index name, add/drop direction) and the default ordering; it does not. Purpose, source, params, and billing are covered, so it is adequate but leaves the agent guessing about result shape for a 5-parameter data tool.

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 every parameter is already documented in the schema. The description's 'Params: ticker, start/end, limit' merely restates them and adds no format, defaulting, or interaction semantics beyond what the schema provides, so baseline 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 description states a specific resource ('Index membership add/drop events') and names its provenance ('derived from public holdings + wiki sources (index_events panel)'), which no sibling tool covers. It is clearly distinguishable from the quote/swap/filings siblings, though it never explicitly contrasts itself with them.

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 statement of when to use this tool versus alternatives, no prerequisites, and no exclusions. The mention of the 'index_events panel' implies a dataset scope but gives the agent no routing guidance among the 20 sibling tools.

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