Purpose: ChatGPT-connector-standard document fetch by id from `search` results.
Namespaces: `tool:{name}` returns the tool's full documentation and how to
call it; `resource:{uri}` returns the resource's live data (core resources
resolved server-side — also the bridge for clients without MCP resource
support, e.g. Gemini); `signal:{market}:{symbol}` returns the symbol's
latest combined research signal.
Triggers: ChatGPT connectors / Deep Research call this after `search`. Clients
without MCP resource support can call it directly with a known resource id,
e.g. fetch("resource:market://global/summary").
When to call: whenever the full content behind a search result id is needed.
Prerequisites: a valid id — from `search` results or a known namespace id.
Next steps: for tool docs, call the named tool via tools/call; for signals,
get_signal_detail / explain_decision for deeper evidence.
Caveats: uncovered resource uris return description-only text (no fabricated
data). `text` is a JSON document for resource/signal ids.
Output: {id, title, text, url, metadata, disclaimer, is_investment_advice,
data_classification} — flat envelope, OpenAI fixed shape.
Args:
id: document id — "tool:{name}", "resource:{uri}", or
"signal:{market}:{symbol}" (market: crypto / kr_stock / us_stock)
Disclaimer: Information only, not investment advice.