Skip to main content
Glama

get_day_board

Read-onlyIdempotent

Which tickers were moving in the last day-trade session? The same-day lane: the names in motion, read in the context of the gate. The morning's day-trade state map: per-name multi-timeframe lights grid (price/RSI/MACD x 5m-1D), GO, FUEL vs anchor ETF, entry-window state and ROOM for 3 names plus 2 per cohort, with the cohort anchors and the reading guide. Day states decay in minutes, so this morning read is a schema/shape preview, not a trading input. Free sample: 3 names plus 2 per cohort, from the morning read.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the description doesn't need to restate safety. It adds real value beyond them: staleness behavior (day states decay in minutes), the sample/cohort size limits, and the fact that cohort anchors and a reading guide are bundled in.

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 opening question front-loads the subject well, but the following three sentences restate the same idea ('the same-day lane', 'the morning's day-trade state map', 'this morning read') and pack in unexplained jargon like GO, FUEL, and ROOM. It is dense rather than tight; the duplication could be cut without loss.

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?

With no output schema, the description must carry the return shape, and it does list the components. However, the shorthand labels (GO, FUEL, ROOM, lights grid) are never defined, and it doesn't say whether the board is dated, cached, or refreshed, which matters for a tool whose own description says the data decays in minutes.

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?

There are zero input parameters, so the baseline is 4. The description does usefully define the output's sampling scope — 3 names plus 2 per cohort, drawn from the morning read — which is the only 'parameter-like' constraint on the call.

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?

The description identifies a specific resource — the morning day-trade state map — and enumerates its contents (per-name multi-timeframe lights grid across price/RSI/MACD x 5m-1D, GO, FUEL vs anchor ETF, entry-window state and ROOM). It is framed as a question rather than a verb+resource and uses proprietary vocabulary, but an agent can still tell this returns a pre-session board snapshot rather than a live feed.

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?

It states a usage boundary clearly: day states decay in minutes, so this morning read is 'a schema/shape preview, not a trading input.' That is a genuine when-not-to-use signal, but it never names the live or as-of alternatives (e.g. get_day_board_live) that an agent should choose for actual trading decisions, leaving the routing inference to the reader.

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