Agent instructions

You use StockContext for US-listed stock and ETF context. It covers NYSE and NASDAQ
listings only: no options, futures, crypto, FX, or non-US equities.

Connection
- Hosted MCP: connect to https://api.stockcontext.com/mcp and send the header
  X-API-Key: $STOCKCONTEXT_API_KEY. Confirm the stockcontext_* tools loaded, then
  smoke-test stockcontext_snapshot with symbol "AAPL". MCP is read-only and calls REST.
- REST: base URL https://api.stockcontext.com, same X-API-Key header on every request.
  When MCP and REST disagree, REST/OpenAPI is the source of truth.

Envelope
- Success is {"data": ...}. Failure is {"error": {"code", "message", "retryable"}}.
- A 200 with freshness "unsupported" plus a machine-readable reason is a real
  answer, not an error. Report it as "not available from StockContext", do not retry it.

Default call sequence
- If the user names a company or fund, call search first to resolve the symbol.
- Call coverage before you store, batch, or deeply analyze a symbol. For
  store-backed SEC facts, branch on support.facts.available_now before calling.
- Call snapshot for most single-symbol questions, then add only what the question
  needs: valuation, fundamentals, facts, events, compare (2-12 tickers),
  filings list -> filing -> filing section or diff for SEC text, insider for
  Form 4/Form 144 activity, technicals + price-action for trend and timing,
  history only when you need a time series.

Plan access
- A Free key calls search, coverage, snapshot, and valuation only. Anything else
  returns PLAN_UPGRADE_REQUIRED (403, not retryable). The snapshot "AAPL" smoke-test
  above works on any plan, including Free.
- Starter and Builder keys reach every public core route and MCP tool.

Output rules
- Answer first. Then show the few facts that support it, then freshness, then the
  calls you made.
- Preserve every value as returned: units, signs, percentages, fiscal periods,
  accessions, filing dates, as_of timestamps, freshness, market_status, and any
  notices or null/unavailable reasons. Never round away a sign or invent precision.
- Never invent data StockContext does not return. Facts can be route-supported
  but not collected yet; ETF holdings are source-state dependent; and segments,
  ownership/13F/13D-G, and governance are private beta, not default public-core
  inputs. If a field or subfamily is missing, report its unavailable reason and
  stop. Analyst consensus or price targets, earnings-call transcripts, options,
  news, and non-US local listings are not available from StockContext.
- A valuation percentile or label (near_5y_low ... near_5y_high, or the _3y_ variants) ranks a
  multiple against THE SAME company's own 3/5/10-year history only. Report it as "low" or "high
  vs its own multi-year range" and name the window the label uses, never as "cheap," "undervalued,"
  "rich," or vs peers/sector/fair value. A multiple can read near_5y_low and still be expensive in
  absolute terms. When a change driver or
  history_regime is present, say WHY the multiple moved (price vs fundamentals) rather than
  quoting the label alone.
- Report priced-in implied growth as "the price is priced for ~X% growth," never as a
  forecast, target, or fair value. Cite the sensitivity range, not just one cell, and compare
  the implied figure to the company's OWN trailing realized growth (history, not a benchmark).
- Treat an absent or unavailable field as deliberate, not an error. A {available: false, reason}
  envelope or an omitted field is a product fact to report, not a gap to fill or retry.
- Summarize SEC risk, MD&A, business, or press-release content only from the filing
  section text StockContext returns. Do not blend in news, consensus, the web, or memory.
- Report data; do not advise. No buy/sell/hold verdict, price target, or trade.

Retry rule
- Retry only when error.retryable is true, and honor Retry-After when present.
  Do not retry UNAUTHORIZED, PLAN_UPGRADE_REQUIRED, SYMBOL_UNKNOWN, SYMBOL_INVALID,
  PARAM_INVALID, PREREQUISITE_MISSING, or an unsupported data state without changing the request.