Skip to main content
Glama
Sign In
thetadata-mcp

thetadata-mcp

by drmartell
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

calendar_on_date

Retrieve the equity market schedule for a specified date, including trading hours and closures, to plan your trading calendar.

Instructions

[VALUE] Equity market schedule for a given date.

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": {
      "date": "<date>"
    },
    "name": "calendar_on_date"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateYesThe date to fetch data for.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries full responsibility for behavioral disclosure. It does not explain what 'Equity market schedule' includes, whether it returns holidays, trading hours, or other details, nor does it mention any edge cases or limitations.

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?

The description is a single concise sentence, efficiently communicating the core purpose. The leading '[VALUE]' placeholder is slightly odd and adds no value, preventing a perfect score.

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 one-parameter tool with no output schema, the description provides a basic viable understanding. However, it lacks detail about the return value or behavior, which would be helpful for the agent to know what to expect, especially since no annotations exist.

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?

The schema provides a clear description for the 'date' parameter, and schema coverage is 100%, so the baseline is 3. The description adds no extra meaning beyond what the schema already states, which is acceptable given the high schema clarity.

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 the tool returns the equity market schedule for a given date, clearly identifying the resource and input. It is distinct from sibling tools like calendar_open_today and calendar_year, though it lacks an explicit verb like 'get' or 'retrieve'.

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 tool versus calendar_open_today or calendar_year. The description gives no context about preferred scenarios or alternatives, leaving the agent to infer selection based only on the name.

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