Skip to main content
Glama
Sign In

Coil Live

by trade.coil
OverviewDiscussionsAdmin

get_sector_read_live

Read-only

How is a sector doing right now, and which stocks lead it? One sector's trend and its leading names, for trading with the money rather than against it. A stock market sector's members scored and ranked from the current session. Live intraday 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

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "sector": "<sector>"
    },
    "name": "get_sector_read_live"
  }
}

Input Schema

NameRequiredDescriptionDefault
sectorYesSector name or sector-ETF symbol

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 read-only/not-destructive, but the description adds meaningful behavior the annotations cannot convey: the payment gate, the fact that failure returns a PaymentRequired object rather than data, and that the data is current-session intraday. It does not describe pagination, latency, or the shape of the returned ranking, leaving some operational gaps.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Purpose is front-loaded in the first two sentences, then payment mechanics follow in a compact block. The only arguably decorative line is the 'with the money rather than against it' framing, which still orients the agent toward a directional/trading read rather than a research lookup.

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 single-required-param read tool with no output schema, the description covers what it returns conceptually ('members scored and ranked'), the auth paths, and the failure mode. A brief note on the fields in the ranking would make it fully self-sufficient, but an agent has enough to call it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and the 'sector' parameter already documents 'Sector name or sector-ETF symbol,' so the description carries no additional parameter meaning. Baseline 3 applies; nothing here tells an agent how to phrase an ambiguous sector name or what happens on a bad value.

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 opening question ('How is a sector doing right now, and which stocks lead it?') is answered immediately with a specific verb+resource: one sector's trend plus its members 'scored and ranked from the current session.' 'Live intraday version' implicitly separates it from the non-live get_sector_read sibling, so an agent can pick correctly without opening the schema.

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?

It gives a clear situational framing ('for trading with the money rather than against it') and, unusually, states the preconditions for using it: a Coil Live subscription with sign-in, or an x402 wallet for pay-per-call. It stops short of naming get_sector_read as the explicit fallback when live data isn't needed or affordable, so the when-not path is only implied.

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

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