Skip to main content
Glama
Crocodile

Crocodile

calendar

Retrieve trading sessions for a crypto or US equity exchange by MIC and date range in UTC, so you can check market open periods and schedule around closures.

Instructions

Trading sessions of one exchange by MIC, in UTC; crypto never closes.

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": {
      "start": "<start>",
      "end": "<end>",
      "asset_class": "<asset_class>"
    },
    "name": "calendar"
  }
}

Input Schema

NameRequiredDescriptionDefault
endYes
micNo
startYes
asset_classYesWhich market answers. Required: this tool has an implementation for each of these and no symbol parameter to infer one from.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.4.0

TDQS

B3/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It does add real behavioral context — results are normalized to UTC, and crypto markets have no close so the calendar is effectively continuous — but it says nothing about the response shape, whether holidays/half-days are included, or what happens with a null MIC.

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?

A single compact sentence with no wasted words and the key qualifiers (MIC, UTC) front-loaded. It is concise to a fault — the terseness is under-specification rather than verbosity.

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 four-parameter, three-required query with no annotations and no output schema, the description covers the target exchange and time zone but omits date formats, the asset_class role, and any indication of what a session record contains. Adequate to identify the tool, insufficient to invoke it confidently.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

At 25% schema coverage the description must compensate, but it only glosses the mic parameter and leaves start/end format and semantics unexplained. The required asset_class enum is never mentioned in the description, and the schema note that dates are strings for GET-compatibility is a schema detail the description does not reinforce.

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?

"Trading sessions of one exchange by MIC, in UTC" names a specific resource (trading sessions), the lookup key (MIC), and the time basis (UTC). An agent can tell this is a market-calendar lookup rather than market data, but the description never explicitly separates it from adjacent catalog/exchange tools.

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 when-to-use or when-not-to-use guidance is given, and nothing points to how to obtain a valid MIC (e.g., the list-exchanges sibling). The only usage-adjacent hint is the aside about crypto never closing, which describes behavior rather than selection criteria.

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