The closure calendar for one exchange: full-day holidays (YYYY-MM-DD, exchange-local) and early-close days with their close times.
| Name | Required | Description | Default |
|---|---|---|---|
| exchange | Yes | Exchange id (e.g. "nyse", "nasdaq", "lse", "nikkei", "hkex") OR common name/city (e.g. "New York Stock Exchange", "Tokyo", "London"). Case-insensitive. |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations indicate readOnly, idempotent, not destructive. The description adds context about date format and early close times, enhancing transparency without contradicting annotations.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single sentence that is concise, front-loaded, and contains all necessary information without redundancy.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool's simplicity (one parameter, no output schema), the description is complete and sufficient for an agent to understand what it does and what to expect.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The single parameter 'exchange' is fully described in the schema with examples and case-insensitivity note. The description does not repeat this but adds no further value; baseline 3 due to 100% schema coverage.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states it returns the closure calendar for one exchange, including full-day holidays and early-close days, which directly matches the tool name and distinguishes it from siblings like is_market_open or get_exchange_status.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implicitly conveys when to use (to get holidays for a specific exchange), but it does not provide explicit guidance on when not to use it or compare directly with alternatives like get_trading_sessions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.