Skip to main content
Glama
Sign In

APIVerve

by com.apiverve
OverviewDiscussionsAdmin

Stock Market Open Times

StockMarketOpenTimes
Read-only

Stock Market Open Times: Stock Market Open Times checks if a global stock exchange is currently trading and provides its opening and closing times. Pass an exchange code like NYSE or LSE to get current open status (open, closed, weekend or holiday), the holiday name, official exchange name, and session hours. On paid plans, add schedule=true for the exchange's local time, half-day early closes, and the next open and close with a countdown in minutes. (Cost: 2 credits)

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": {
      "exchange": "<exchange>"
    },
    "name": "StockMarketOpenTimes"
  }
}

Input Schema

NameRequiredDescriptionDefault
exchangeYesThe stock exchange code
scheduleNoInclude local time, half-day early close, next open and close, and minutes until the next change

Output Schema

NameRequiredDescriptionDefault
dataNo
errorNoError message, null on success
statusNo"ok" on success

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds real context beyond that: a 2-credit cost, a paid-plan gate on schedule=true, and the enumerated status values including holiday and weekend states. It does not mention rate limits or failure behavior for an unknown exchange code, so it falls just short of top marks.

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 the purpose, then inputs, then optional paid features and cost — a logical order with no filler. The only waste is the redundant restatement of the tool name at the start of the first sentence.

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

Completeness5/5

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

For a two-parameter read-only lookup, it covers the required input format, the optional flag's effects, the response fields, the paid-plan gate, and the credit cost. With an output schema also present, nothing an agent needs in order to call this correctly is missing.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3. However, the description earns more by explaining that exchange takes codes like NYSE or LSE and by spelling out what enabling schedule actually unlocks (local time, half-day early closes, next open/close with a countdown in minutes) — richer than the schema's one-line description of the flag.

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?

States a specific verb and resource: checks whether a global stock exchange is currently trading and returns open/close times. It also enumerates the returned status values (open, closed, weekend, holiday), which makes the purpose concrete. It does not differentiate itself from nearby siblings such as GlobalStockMarket or StockExchange, which keeps it short of a 5.

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

Usage Guidelines4/5

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

Gives clear invocation guidance: pass an exchange code such as NYSE or LSE, and add schedule=true to unlock the richer payload. It also flags that schedule is gated behind paid plans, which is actionable context. It offers no explicit when-not-to-use guidance or named alternatives, so it stops at 4.

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

All APIVerve toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources