Skip to main content
Glama

NightWatch Live Intelligence

forge_signal_plan

Turn one Forge signal into a concrete order plan for YOUR OWN mirrored account (docs/pm/SIGNAL_MIRRORING.md §2.2). Requires signal_id and an active mirror on that vault (consent first via POST /forge/vaults/{id}/mirrors or the forge_mirror_consent tool); pass account_address only if you have more than one active mirror on that vault. Planning a LIVE signal costs the same as reading it, 10🍒 or $0.10 in USDC over x402 (Cherry -> x402; the free reads never cover it) — free if you already paid to read this exact signal; a plan against a signal older than 24h is always free. The response's charged field says whether THIS call was the one that paid, and historical says whether the signal itself is no longer live (a plan against history is still fully computed, but is not a current instruction). Sizes the order to your account's own NAV at the current mark, checks it against your own caps and the vault's mandate, and refuses it with a reason if it would breach either — including when the vault's own book is currently mirroring_paused (a charge, if any, still happens even when the plan comes back refused this way — see charged; a refusal because a later signal has superseded this one is the one exception and is never charged). This call NEVER places an order; execute the returned plan yourself with your own trade-only agent key, then report the fill with POST /forge/signals/{signal_id}/fills (account_address, filled_at, price, qty, side, and venue_order_id if you have one) — a plain write, no charge, no flag, works for any follower mirroring in their OWN account, and shows up in GET /forge/vaults/{id}/mirrors/me with source:'self_report'. The Torii-linked path (POST /torii/order with sign_mode:'client', then POST /torii/order/record with confirm_id/outcome/this signal's id) is an optional alternative that works ONLY for NightWatch's own single configured operator account (needs NW_TORII_LIVE_ENABLED and that account's own allowlisted key) — an outside follower's own account cannot authenticate to it at all; use the fills endpoint above instead. R78 liquidity safety: for an HL perp market, the plan also refuses new exposure below NW Grade C, caps a single order by both 24h volume and order-book depth (scaling it down, never up), and gates a stock-underlying perp (trade.xyz) to its cash market's hours when its grade is C or provisional. A trim or delisting-close exit signal is evaluated as a REDUCTION — exempt from the grade floor and the session gate — only when your own live position on that market opposes the order and can be read; otherwise ordinary new-exposure rules apply and the exit can be refused too. The response's grade, provisional, capped_notional_usd, impact_bps, session (with next_open when closed), and disposition/retry_at say which and why. A session-deferred plan (disposition:'deferred') is NOT retried for you — that automatic retry is the maker's own passive engine acting on the maker's own legs; call this tool again yourself at session.next_open.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
signal_idYesForge signal id (from forge_signals)
mandate_idNoOptional: mandate public id, e.g. m_irifvvp7rr. Sizes the plan inside that Torii Wallet mandate (sent to POST /forge/signals/{id}/plan as mandate_id).
account_addressNo0x... — only needed to disambiguate when you have more than one active mirror on this signal's vault

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / mandate_id
      Added value: +{
      +  "description": "Optional: mandate public id, e.g. m_irifvvp7rr. Sizes the plan inside that Torii Wallet mandate (sent to POST /forge/signals/{id}/plan as mandate_id).",
      +  "type": "string"
      +}
  2. Added

TDQS

A4.3/5.0
Behavior4/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 richly: pricing (10🍒/$0.10 x402, free cases), charge semantics (`charged`/`historical`), refusal conditions including mirroring_paused, the explicit 'NEVER places an order' guarantee, and the reduction-vs-new-exposure rule for trim/delisting signals. It stops short of exhaustive failure/retry mechanics for every refusal class but covers far more than typical.

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?

Front-loaded correctly (purpose, then requirements, pricing, safety), and most sentences carry real information. However it is one dense block riddled with nested parentheticals and em-dash asides that make it hard to scan; a few clauses could be tightened without losing meaning.

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?

For a complex, mutation-adjacent, paid tool with no annotations and no output schema, the description covers requirements, cost, refusal semantics, and even enumerates the response fields (charged, historical, grade, capped_notional_usd, impact_bps, session/next_open, disposition/retry_at). Nothing an agent needs to call it correctly appears missing.

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 documents all three parameters; the description reinforces signal_id and clarifies when account_address is required (multiple active mirrors), adding modest value. mandate_id is described only in the schema and never referenced in the prose, so the description does not meaningfully exceed the structured fields.

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+resource scope ('Turn one Forge signal into a concrete order plan for YOUR OWN mirrored account') and immediately distinguishes it from the fill-reporting and Torii order paths named later. An agent can tell this is planning-only and place it apart from forge_signals, forge_signal_fill, and forge_signal_publish without opening a schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly states prerequisites (active mirror, consent via forge_mirror_consent), when account_address is needed, and when alternatives apply — it names the fills endpoint and the Torii path and rules the latter out for outside followers ('an outside follower's own account cannot authenticate to it at all; use the fills endpoint above instead'). When-to-use, when-not-to-use, and alternatives are all present.

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.