NythosX Market Data

arm_price_trigger

Arm a price trigger with webhook delivery. Arms a single-fire price trigger. NythosX checks the price every minute and POSTs a JSON event to your HTTPS webhook on the first crossing: {event:"trigger.fired", id, symbol, direction, price, fired_price, fired_at}, signed with HMAC-SHA256 (header X-NythosX-Signature: sha256= over the raw body, key = returned secret). Retries up to 5 times (8s timeout per attempt, until your endpoint returns 2xx); after 5 failed attempts delivery is marked failed — check status free with get_trigger_status (REST: GET /api/v1/triggers/status?id=) to see delivery_attempts/last_error. Expires after ttl_hours (default 168, max 720); cancel any time before it fires, free, with disarm_price_trigger (REST: POST /api/v1/triggers/cancel with {id, secret}) — the arm fee is not refunded, it paid for the monitoring already done. Costs $0.02 USDC per call (x402).

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>",
      "direction": "<direction>",
      "price": "<price>",
      "webhook_url": "<webhook_url>"
    },
    "name": "arm_price_trigger"
  }
}

Input Schema

Name	Required	Description
`price`	Yes
`symbol`	Yes	Instrument symbol
`direction`	Yes
`ttl_hours`	No
`webhook_url`	Yes	Public HTTPS URL that receives the signed trigger.fired event

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 20, 2026

TDQS

A4.6/5.0

Behavior5/5

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

With no annotations, the description carries the full burden and does so: minute-level polling, exact POST payload shape, HMAC-SHA256 signing header, 5 retries at 8s timeout, failure marking, TTL default/max, and non-refundable arm fee. This is unusually complete behavioral disclosure.

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?

Dense single paragraph, front-loaded with the core action and followed by operational details in a logical order (delivery, retries, status, expiry, cancel, cost). Every clause is informative, though the parenthetical REST endpoints add bulk that could be trimmed.

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?

Despite no output schema, the description discloses what is returned (secret), how the callback is verified, and the full cost/expiry/cancel lifecycle. Nothing material for correct invocation is missing.

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 40%, and the description compensates by defining ttl_hours semantics (default 168, max 720) and webhook_url requirements (public HTTPS, receives signed event), plus the returned secret. Symbol/direction/price meaning is left to the schema enums, which is reasonable.

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 verb and resource ('Arm a single-fire price trigger with webhook delivery') and immediately scopes it as single-fire, distinguishing it from the status/cancel siblings. An agent knows exactly what this creates 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?

Gives clear conditions: use this to arm monitoring, use get_trigger_status (free) to check delivery, use disarm_price_trigger to cancel before firing. It does not explicitly exclude other cases (e.g., one-off price checks via get_free_snapshot), but the routing guidance is concrete.

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

All NythosX Market Data tools Inspect

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

Need Help?