Skip to main content
Glama
choaticpixels

Wicked API - Agent First API Services

market_clock

Check the current US equities market status, next open/close times, and upcoming trading sessions.

Instructions

US equities market clock (is_open, next_open/close) + upcoming sessions, via Alpaca — US equities market clock (is_open, next_open/close) + upcoming sessions, via Alpaca. Crypto endpoints are 24/7 and unaffected.

Example: /v1/market-clock

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
daysNoOptional. Upcoming session days to include (default 3, max 30; 0 to omit).
Behavior3/5

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

No annotations provided, so description bears full burden. It mentions 'via Alpaca' implying external dependency, and states crypto is 24/7, but does not disclose authentication needs, rate limits, or any side effects. Adequate but not rich.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is short but contains a redundant sentence (first sentence repeated). The example adds value but could be integrated. Some waste, but overall concise.

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

Completeness4/5

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

For a simple read-only tool with one optional parameter and no output schema, the description adequately explains the output (is_open, next_open/close, upcoming sessions). It covers the essential behavioral context.

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 covers 100% of the single optional parameter 'days'. The description does not add any meaning beyond the schema's own description. Baseline 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 it provides a US equities market clock with open/close times and upcoming sessions. It distinguishes from siblings by specifying it's a clock, not price/volume data. The repeated sentence reinforces the purpose.

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 explicit guidance on when to use this tool versus alternatives. Since there is no sibling clock tool, the need is lower, but the description still lacks usage context or prerequisites.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/choaticpixels/WickedAPI_MCP'

If you have feedback or need assistance with the MCP directory API, please join our Discord server