Skip to main content
Glama

get_rotation_live

Read-only

Which sectors are leading right now, on the live board? Where the money is moving: the sectors and asset classes leading and lagging, the second step of a top-down read. X/SPY leadership states (GO / HOLDING / TURNING / OUT) for the 11 sector ETFs and every macro-book instrument (bond, income, metals and commodity ETFs plus a few single stocks such as the gold and copper miners), recomputed on the live board during market hours. The payload's reading field notes that confirmed rotation is late for a pullback buyer. 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_rotation_live"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already establish readOnly/openWorld/non-destructive, so the description's real contribution is auth and failure behavior: subscription or x402 per-call payment, and that it returns a PaymentRequired object with no data otherwise. It also discloses data freshness (recomputed during market hours) and the meaning of the `reading` field, which is genuinely useful context beyond the annotations.

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?

Purpose is front-loaded, but the body is a run-on of fragments ('Where the money is moving: ...'), and 'live' is repeated several times ('on the live board,' 'live board during market hours,' 'Live version'). The detached one-word-ish sentence 'Live version.' adds little and disrupts flow.

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

Completeness4/5

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

For a zero-parameter read with no output schema, the description covers what the payload measures, its cadence, one named payload field, and the access/failure path — enough for an agent to call it correctly. It stops short of describing the payload's overall shape or size, which is the main remaining gap.

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 no parameter meaning to add; baseline is 4. The description does not waste space pretending otherwise and instead spends its words on payload and access semantics.

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 names the specific resource and question it answers: sector/asset-class leadership and laggards, computed as X/SPY leadership states (GO / HOLDING / TURNING / OUT) across the 11 sector ETFs plus macro-book instruments. 'Live version' plus 'recomputed on the live board during market hours' implicitly separates it from the non-live `get_rotation` sibling, though the sibling is never named explicitly.

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 provides implied usage context as 'the second step of a top-down read,' which helps an agent place it in a workflow, and it states the access prerequisites (Coil Live subscription or x402 wallet). It never explicitly says when to prefer this over `get_rotation` or `get_board_asof`, and gives no exclusions.

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