Skip to main content
Glama
Sign In
Wicked MCP server

Wicked MCP server

by WickedAPI
OverviewSchemaSourceRelated ServersDiscussions(1)Admin
TypeScript
Hybrid

market_clock

Read-onlyIdempotent

Check whether US equity markets are open and retrieve the next open or close time plus upcoming session days for trading-hours decisions. Crypto trades 24/7 and is unaffected.

Instructions

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

Example: /v1/market-clock

Use when you need to know whether US equity markets are open and when the next session opens or closes. Not for crypto, which trades 24/7.

Behavior: read-only. Priced via x402 (USDC on Base) or free with WICKEDAPI_API_KEY; with neither, you get HTTP 402 with the decoded price in payment_required (a price quote, not a failure).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "market_clock"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNoOptional. Upcoming session days to include (default 3, max 30; 0 to omit).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.1

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already cover the safety profile (readOnlyHint, idempotentHint, openWorldHint), and the description adds materially new behavioral facts beyond them: payment via x402 (USDC on Base) or free with WICKEDAPI_API_KEY, and crucially that an HTTP 402 response carries the decoded price in payment_required and is a quote, not a failure. That last point prevents an agent from misinterpreting a normal response as an error.

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?

Front-loaded with purpose in the first sentence, then example endpoint, usage rule, and behavior — a clean, scannable structure. It loses a point for redundancy: "Crypto endpoints are 24/7 and unaffected" and "Not for crypto, which trades 24/7" say the same thing twice.

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?

With no output schema, the description still names the key return fields (is_open, next_open/close) and explains the non-obvious 402 payment flow, which is enough for correct invocation. It does not describe the shape of the upcoming-sessions list or pagination/limits, a minor gap for a single-parameter read tool.

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 description coverage is 100% and the single optional `days` parameter is fully documented in the schema (default 3, max 30, 0 to omit). The description only implies that upcoming sessions are configurable via "+ upcoming sessions" and adds no syntax or default detail beyond the schema, so the baseline 3 applies.

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?

States a specific verb+resource: returns the US equities market clock (is_open, next_open/close) plus upcoming sessions, sourced via Alpaca. It explicitly bounds scope to US equities and declares crypto out of scope, so an agent can distinguish it from the other 24/7 crypto price/OHLCV tools in the sibling list.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

"Use when you need to know whether US equity markets are open and when the next session opens or closes" gives the positive selection condition, and "Not for crypto, which trades 24/7" gives the exclusion. Both directions are stated explicitly rather than left to inference.

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