Skip to main content
Glama

get_day_board_live

Read-only

Which tickers are moving right now? The same-day lane: the names in motion, read in the context of the gate. LIVE day-trade state map (~5 min refresh in market hours): 18-cell lights grid, GO, FUEL vs the tab's anchor ETF, efficiency, ATR%, vs-SPY, entry-window state and ROOM (% + bars to the nearest overhead level) on ~70 liquid names. A STATE MAP, not a ranking; all-lit boards flag ext:true (late). Live version. Coil Live is a subscription with a 7-day free trial; subscribers connect the Coil Live connector and sign in, and this read returns live data. Agents with an x402 wallet can also pay per call. Without a subscription or an x402 wallet it returns a PaymentRequired object and no data.

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": "get_day_board_live"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior5/5

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

Beyond the annotations, the description discloses refresh cadence (~5 min in market hours), the access model (subscription with 7-day trial, connector sign-in, or x402 pay-per-call), and the exact failure mode: without entitlement it returns a PaymentRequired object and no data. It also explains that all-lit boards flag ext:true, which is behavior an agent would otherwise misread.

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?

The leading question front-loads the purpose, and the entitlement paragraph is dense but necessary since there is no output schema to convey it. There is minor redundancy — 'LIVE' is stated, then 'Live version.' repeated — and the jargon-dense field list reads as a run-on, but each element carries information.

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?

With no output schema and no parameters, the description carries the full burden and meets it: it enumerates what the payload contains, the universe size, the refresh rate, the meaning of the ext:true flag, and the payment-required failure path. An agent can decide to call it and interpret the result without further documentation.

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?

The tool takes zero parameters, so the baseline is 4; there is nothing for the description to disambiguate. The field enumeration (GO, FUEL, ROOM, entry-window state) describes output content rather than inputs, which is handled under other dimensions.

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 opens with a concrete question the tool answers and names the resource precisely: a LIVE day-trade state map of ~70 liquid names with specific readouts (lights grid, GO, FUEL vs anchor ETF, ATR%, ROOM). It also pre-empts a likely misread by stating 'A STATE MAP, not a ranking', and the 'Live version' line separates it from the non-live get_day_board.

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

Usage Guidelines3/5

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

Usage is implied through 'The same-day lane: the names in motion' and the live/intraday framing, which tells an agent this is for real-time day-trade context. However, no sibling is named explicitly and there is no explicit when-not guidance (e.g. versus get_day_board for end-of-day or get_buy_list_live for curated entries), so the agent must infer the routing.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources