Skip to main content
Glama

get_hold_state_live

Read-only

Is the trend behind a position I own still intact right now? For a position already owned: whether the trend behind it is intact, weakening or broken. Live SELL-SIDE read on names you already hold: current-session trend state, hold strength, readiness, maturity-late flag, gap-risk grade, book regime, and watch_flags naming which deterioration conditions are true right now. Up to 10 symbols per call. Reports conditions only; it never reads your entry or size. 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": {
      "symbol": "<symbol>"
    },
    "name": "get_hold_state_live"
  }
}

Input Schema

NameRequiredDescriptionDefault
symbolYesTicker, e.g. NVDA — or up to 10 comma-separated (NVDA,AMD,BTC-USD)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior5/5

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

Beyond the annotations, the description discloses live-data access through the Coil Live connector, subscription requirements with a 7-day trial, x402 pay-per-call access, and the specific failure mode of returning a PaymentRequired object with no data. It also clarifies that the tool reports conditions only and does not read entry or size.

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?

The description is front-loaded with the primary question and then provides operational details. There is some redundancy between the opening question and the following 'For a position already owned' sentence, but the payment and scope information is valuable and generally well organized.

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?

Although no output schema is provided, the description enumerates the returned conditions and flags sufficiently for an agent to understand what the call yields. It also covers authentication, payment gating, symbol limits, and the no-data PaymentRequired response, making it complete for this tool's complexity.

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%, so the schema already defines the symbol parameter and the comma-separated format. The description repeats the 'up to 10 symbols per call' limit but adds no additional syntax or semantic detail beyond the schema.

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 description states a specific read operation over held positions and enumerates the exact outputs: current-session trend state, hold strength, readiness, maturity-late flag, gap-risk grade, book regime, and watch_flags. It also labels itself the 'Live version' and a 'SELL-SIDE read on names you already hold', which distinguishes it from the non-live hold-state sibling.

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?

The description clearly frames the use case: positions already owned, live sell-side conditions, up to 10 symbols per call, and explicitly says it never reads entry or size. It implies the live-vs-non-live distinction via 'Live version' but does not explicitly explain when to choose the non-live counterpart.

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