Skip to main content
Glama

get_full_board

Read-only

The complete live board in one payload: every scored name (650+ across S&P 500, Nasdaq-100, macro), sector lanes, both buy-list lanes, regime and crypto books. Every name carries its coil read (coil_score / coil_kind / coil_note) and the payload carries the awareness block (leaders, sector flows, coiled, coverage). Fields are self-described in the payload's schema block (key · tier · description · since). dip: {ok, codes, setup}: present only for oversold-pullback candidates; a dip buy only on a completed hourly turn above the entry-quality and depth floors. 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_full_board"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint=true, destructiveHint=false), so the bar is lower, and the description still adds meaningful behavior: the payload's awareness block, the self-describing `schema` block, the conditional `dip` object and its hourly-turn gating rule, and critically the payment gating that returns a PaymentRequired object with no data. The one gap is that idempotentHint=false goes unmentioned despite the read being live/streaming in nature.

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 payload contents before the access and payment caveats, and the dense field lists are justified for a 650+ name board. The fragment 'Live version.' is low-value and slightly interrupts the flow, and the subscription/x402 sentences could be tightened, but nothing is truly extraneous.

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?

There is no output schema, so the description carries the return-value burden and does so well: it names the major sections, explains the awareness block, points to the embedded `schema` block for self-described fields, and defines the conditional `dip` object. It also closes the biggest operational unknown by explaining the subscription/trial/x402 payment path and the PaymentRequired failure mode.

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 there is nothing to disambiguate and the baseline is 4. The description's field-level detail about the payload (coil_score/coil_kind/coil_note, dip: {ok, codes, setup}) describes returns rather than inputs, so it does not lift the score further.

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 resource and scope: 'The complete live board in one payload' covering every scored name (650+ across S&P 500, Nasdaq-100, macro), sector lanes, both buy-list lanes, and regime and crypto books. The 'complete ... in one payload' framing implicitly distinguishes it from the per-lane siblings like get_sector_read or get_buy_list_live without needing to open either schema.

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 only implied: the 'one payload' framing suggests it is the aggregate read, but the description never explicitly says when to choose it over get_day_board_live, get_sector_read_live, or the other lane tools, nor when to prefer a narrower call. The access path (subscription vs x402 wallet) is described, but that is availability, not use-case guidance.

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