NythosX Market Data

disarm_price_trigger

Cancel a trigger armed with arm_price_trigger, before it fires (free). Requires both id and secret — the same token returned once at arm time and used to verify the webhook's HMAC signature — as proof of ownership. The $0.02 arm fee is not refunded; it paid for the monitoring already done. Returns 404 for an unknown id/secret pair, 409 if the trigger already fired or was already cancelled.

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": {
      "id": "<id>",
      "secret": "<secret>"
    },
    "name": "disarm_price_trigger"
  }
}

Input Schema

Name	Required	Description	Default
`id`	Yes
`secret`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 27, 2026

TDQS

A4.7/5.0

Behavior5/5

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

With zero annotations the description carries the full burden and does so: it discloses the cost model (free, $0.02 arm fee not refunded and why), the ownership/authentication requirement (id + secret, HMAC proof), and failure semantics (404 unknown pair, 409 already fired or cancelled). This is exactly the mutation-risk context an agent needs before calling.

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?

Four sentences, front-loaded with the action and its precondition, followed by cost, auth, and error semantics in priority order. Every clause carries information — even the parenthetical HMAC note exists to tell the agent where the secret comes from.

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 two-param mutation with no annotations and no output schema, the description covers safety, auth, cost, and error outcomes thoroughly. The only gap is the success return shape (what the 200 response contains), which is a minor omission rather than a blocker.

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

Parameters5/5

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

Schema coverage is 0%, so the description must compensate, and it does: 'id' is implicitly the trigger identifier and 'secret' is defined as the token returned once at arm time and used to verify the webhook's HMAC signature, i.e. proof of ownership. Both undocumented params gain real meaning and a source for the 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?

States a specific verb and resource ('Cancel a trigger') plus the precise scope ('armed with arm_price_trigger, before it fires'), which immediately separates it from the arming sibling and from get_trigger_status. An agent can route correctly without opening any 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?

Names the originating tool (arm_price_trigger) and the timing condition ('before it fires'), and the '(free)' marker signals when this is the cheap alternative to letting it run. It stops short of explicitly directing the agent elsewhere for status checks or post-fire handling, but the usage context is clear.

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?