Skip to main content
Glama

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

A3.6/5.0
Behavior4/5

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

Annotations already cover read-only and open-world semantics, and the description goes well beyond them by disclosing the access model: a subscription with a 7-day free trial, connector sign-in, and an x402 per-call payment alternative. It also names the exact failure mode — a PaymentRequired object with no data — which is precisely the kind of behavioral detail annotations cannot convey. Only freshness/latency and pagination or result size are left unstated.

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 payment/access information is front-loaded well enough, but the opening two sentences overlap ('which stocks lead it' then 'its leading names') and 'for trading with the money rather than against it' is promotional filler. The definition could shed roughly a third of its text without losing any operative detail.

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-parameter read with full schema coverage and no output schema, the description supplies what an agent needs: what is returned conceptually (scored and ranked members, trend, leading names), that data is live/current-session, and what happens without entitlement. It stops short of describing response shape or how many leaders are returned, which is a minor gap given no output schema exists.

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 single parameter already documents itself as 'Sector name or sector-ETF symbol.' The description adds no syntax, accepted-value, or naming-convention detail beyond the schema, so the baseline of 3 applies even though the phrase 'One sector's' reinforces that exactly one sector is queried per 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 states a specific resource and outcome: 'One sector's trend and its leading names' and 'A stock market sector's members scored and ranked from the current session.' It distinguishes the live variant from the non-live sibling only with the terse phrase 'Live version,' but combined with the title 'Sector read (live)' an agent can still tell which resource it reads.

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?

'For trading with the money rather than against it' implies a directional/trend-following use case rather than an explicit when-to-use rule. There is no guidance on when to pick this over get_sector_read, get_market_leaders_live, or get_rotation_live, and no stated exclusions beyond the payment prerequisite. Usage is implied rather than prescribed.

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