Skip to main content
Glama

Twelvedata

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Earnings Calendar

earnings_calendar
Read-onlyIdempotent

Twelve Data broad earnings calendar — upcoming and recent earnings announcements across all covered symbols. Returns symbol, date, EPS estimate, and time of day (before/after market).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
end_dateNoOptional end of range, "YYYY-MM-DD" or "YYYY-MM-DD HH:MM:SS".
start_dateNoOptional start of range, "YYYY-MM-DD" or "YYYY-MM-DD HH:MM:SS".

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
codeNoResponse code
statusNoResponse status
messageNoResponse message

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / end_date
      Added value: +{
+  "description": "Optional end of range, \"YYYY-MM-DD\" or \"YYYY-MM-DD HH:MM:SS\".",
+  "type": "string"
+}
    • addedInput schema / properties / start_date
      Added value: +{
+  "description": "Optional start of range, \"YYYY-MM-DD\" or \"YYYY-MM-DD HH:MM:SS\".",
+  "type": "string"
+}
  2. Changed1 schema field changed
    • removedInput schema / additionalProperties
      Removed value: -true
  3. Changed2 schema fields changed
    • addedInput schema / examples
      Added value: +[
+  {}
+]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "code": {
+      "description": "Response code",
+      "type": "number"
+    },
+    "message": {
+      "description": "Response message",
+      "type": "string"
+    },
+    "status": {
+      "description": "Response status",
+      "type": "string"
+    }
+  },
+  "type": "object"
+}
  4. First observed

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint false. The description adds that it returns symbol, date, EPS estimate, and time of day, which provides behavioral context beyond annotations but does not disclose any restrictions or side effects.

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?

The description is two concise sentences with no wasted words. It front-loads the purpose and then lists return fields efficiently.

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

Completeness5/5

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

Given the output schema exists and annotations cover safety and open-world behavior, the description sufficiently explains the tool's scope (all symbols, upcoming and recent) and return values. It is complete for a simple calendar tool with optional parameters.

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?

Both parameters (start_date, end_date) have descriptions in the input schema, achieving 100% coverage. The description does not add extra meaning beyond what the schema already provides, so a baseline score of 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?

The description clearly states the tool provides a broad earnings calendar with upcoming and recent announcements across all covered symbols, and specifies the return fields (symbol, date, EPS estimate, time of day). This distinguishes it from sibling tools like 'earnings' by emphasizing broad coverage.

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?

No guidance is given on when to use this tool versus alternatives (e.g., 'earnings' for specific symbols). The description lacks explicit context about appropriate use cases or exclusions.

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

All Twelvedata 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