Skip to main content
Glama

Coil Scanner

by trade.coil
OverviewDiscussionsAdmin

get_engine_feed

Read-onlyIdempotent

THE COIL LIVE FEED: the engine-grade board Coil's live record trades from, a superset of the complete live board that adds per-name structural stop and target levels, stop/target basis, risk-reward, buy_score, conviction, lane, leveraged vehicle and ladder placement (engine_fields, including coil_score / coil_kind). Optional symbols[] filter. Size, measured on ~800 names: unfiltered ≈1.35 MB (hundreds of thousands of tokens); a 2-name symbols read ≈70 KB; the same read with compact=true ≈12 KB; compact=true for the whole board ≈350 KB. Optional fields[] picks engine fields; limit and cursor page the names by symbol. Refreshed about every 5 minutes in market hours; identical for every subscriber; research, not advice. Engine fields are self-described in the payload's schema block (key · tier · description · since; omitted when compact=true). 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.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoOptional: page size, names per page (sorted by symbol). The response carries page.next_cursor.
cursorNoOptional: the page.next_cursor from the previous page (the last symbol returned). Omit for the first page.
fieldsNoOptional: keep only these engine_fields keys per name (e.g. ["stop","target","rr"]). Unknown keys are echoed in unknown_fields. With compact=true this replaces the core engine-field set.
compactNoOptional, default false (the full payload, unchanged). true = core fields only: names[] and engine_fields[] keep the core keys, and the fixed context blocks (schema, rotation, awareness, perf, pair_rotation, books beyond regime, day rows/cohorts) are dropped. candidates[], freshness and rules_version always ride.
symbolsNoOptional: trim names + engine_fields to these tickers (max 50)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / properties / compact
      Added value: +{
+  "description": "Optional, default false (the full payload, unchanged). true = core fields only: names[] and engine_fields[] keep the core keys, and the fixed context blocks (schema, rotation, awareness, perf, pair_rotation, books beyond regime, day rows/cohorts) are dropped. candidates[], freshness and rules_version always ride.",
+  "type": "boolean"
+}
    • addedInput schema / properties / cursor
      Added value: +{
+  "description": "Optional: the page.next_cursor from the previous page (the last symbol returned). Omit for the first page.",
+  "type": "string"
+}
    • addedInput schema / properties / fields
      Added value: +{
+  "description": "Optional: keep only these engine_fields keys per name (e.g. [\"stop\",\"target\",\"rr\"]). Unknown keys are echoed in unknown_fields. With compact=true this replaces the core engine-field set.",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}
    • addedInput schema / properties / limit
      Added value: +{
+  "description": "Optional: page size, names per page (sorted by symbol). The response carries page.next_cursor.",
+  "maximum": 1000,
+  "minimum": 1,
+  "type": "integer"
+}
  2. Added

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already cover the safety profile (readOnly, idempotent, destructive false), and the description goes well beyond them: concrete payload sizes for filtered/compact/unfiltered reads, ~5-minute refresh in market hours, identical-for-all-subscribers semantics, auth/subscription requirements, and the compact=true effect on the embedded schema block.

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-loads the identity ('THE COIL LIVE FEED') and keeps the operational facts (size, cadence, auth, paging) in one dense block. It is long and slightly repetitive about the schema block and compact behavior, but nearly every sentence carries actionable detail.

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, the description carries the return-shape burden and does so: it names the engine_fields, the self-describing payload `schema` block (key · tier · description · since), the blocks dropped under compact, and what always rides along. Auth, cadence, and sizing are all present, leaving no material gap for correct invocation.

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 schema already defines each parameter; the description adds consequence-level meaning the schema lacks, e.g. ~1.35 MB unfiltered vs ~70 KB for two symbols vs ~12 KB with compact=true, and that fields[] selects engine field keys while compact=true uses the core set.

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 (the Coil live engine-grade board) and explicitly positions it as 'a superset of the complete live board that adds per-name structural stop and target levels, ... buy_score, conviction, lane, leveraged vehicle and ladder placement'. That superset framing lets an agent distinguish it from siblings like get_full_board or get_day_board_live without opening schemas.

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 context: it is the engine-grade board, and it documents the subscription prerequisite (subscribers connect the Coil Live connector and sign in) plus refresh cadence. However it never names a sibling alternative or an explicit when-not condition, so the routing guidance is implicit rather than spelled out.

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

All Coil Scanner 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