Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List Yahoo Finance calendar

yahoo_finance_calendar_list
Read-onlyIdempotent

Retrieve Yahoo Finance earnings, economic, split, and IPO calendar rows for a required date range. Filter by region or calendar type to plan event-driven research and market analysis.

Instructions

List Yahoo Finance earnings, economic, split and IPO calendar rows. Requires from and to. Returns a list (use cursor when paginated).

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": {
      "from": "<from>",
      "to": "<to>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "yahoo_finance_calendar_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
toYesRequired. Window end: an ISO 8601 date or time. It is exclusive. Epoch seconds are also accepted.
fromYesRequired. Window start, as an ISO 8601 date or time (such as `2026-01-31`) or epoch seconds. A time with no zone is UTC.
typeNoCalendar: `earnings`, `economic`, `splits` or `ipo`. Default: `earnings`.
limitNoPage size as an integer from 1 to 250. Default: 100.
cursorNoCursor from `page.nextCursor` of the previous response. It only works with the same filters.
offsetNoZero-based position to begin the list at. Default: 0; maximum: 1,000,000. Only the first 10,000 rows are available; past that the page is empty.
regionNoMarket region, a two-letter code such as `US`, `GB` or `JP`.
contextYesDescribe the user's underlying goal in one sentence, not the tool you are calling.
languageNoLanguage tag for names and news, e.g. `en-US` or `ja-JP`.
llm_modelYesThe exact model identifier you (the assistant) are running as, taken from your system prompt or environment (for example "claude-opus-4-8" or "gpt-5.2"). Used for analytics only. If you do not know your model identifier with certainty, pass "unknown" and do not guess.
conversation_idNoEcho the conversation_id from the server's previous response. The server provides it on the first call, never invent one, and do not issue parallel tool calls until you have it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is fully covered by structured data. The description adds that the result is a list and that a cursor should be used when paginated, which is modest but real context beyond the annotations; it says nothing about rate limits, auth, or the 10,000-row offset ceiling.

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?

Three short sentences, front-loaded with purpose followed by the prerequisite and the return shape. Slight redundancy with the schema (both `from` and `to` are already marked required), which keeps it from a 5, but there is no filler.

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 11 parameters and no output schema, the description covers what is listed and how pagination continues, but it omits scoping dimensions that matter for this tool (region, language, the 10,000-row cap) and says nothing about the conversation_id sequencing the schema requires. Adequate minimum viable coverage, not complete.

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 (including `cursor`, `offset`, `limit`, `region`, `language`) is already documented in the schema. The description only restates the `from`/`to` requirement and the cursor pagination hint, adding no new semantics such as date-format examples or interaction between cursor and offset. Baseline 3 applies when the schema does the heavy lifting.

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?

States a specific verb (List) and resource (Yahoo Finance calendar rows), and enumerates the four calendar kinds (earnings, economic, split, IPO), which lets an agent distinguish it from the resource-specific siblings like yahoo_finance_earnings_get or yahoo_finance_quotes_list. It stops short of explicitly naming an alternative it is not, so it falls just below a 5.

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?

"Requires `from` and `to`" gives a hard prerequisite and the type enumeration implies which calendar to pick, but there is no explicit when-to-use versus when-not guidance and no mention of region scoping or how this differs from the *_get siblings. Usage is inferable rather than stated.

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