OneQAZ Trading Intelligence

Fetch Document

fetch

Read-onlyIdempotent

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.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`id`	Yes	document id — "tool:{name}", "resource:{uri}", or "signal:{market}:{symbol}" (market: crypto / kr_stock / us_stock)

Output Schema

TableJSON Schema

Name	Required	Description	Default
`id`	No
`url`	No
`text`	No
`title`	No
`metadata`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 7, 2026
- addedInput schema / additionalProperties
```
Added value: +false
```

Changed2 schema fields changedSep 23, 2026

addedOutput schema / description

Added value: +"`full_data` for fetch — 실응답에서 추출(2026-09-23)."

addedOutput schema / properties

Added value: +{
+  "id": {
+    "anyOf": [
+      {
+        "type": "string"
+      },
+      {
+        "type": "null"
+      }
+    ],
+    "default": null
+  },
+  "metadata": {
+    "additionalProperties": true,
+    "type": "object"
+  },
+  "text": {
+    "anyOf": [
+      {
+        "type": "string"
+      },
+      {
+        "type": "null"
+      }
+    ],
+    "default": null
+  },
+  "title": {
+    "anyOf": [
+      {
+        "type": "string"
+      },
+      {
+        "type": "null"
+      }
+    ],
+    "default": null
+  },
+  "url": {
+    "anyOf": [
+      {
+        "type": "string"
+      },
+      {
+        "type": "null"
+      }
+    ],
+    "default": null
+  }
+}

Changed1 schema field changedSep 22, 2026

addedInput schema / properties / id / description

Added value: +"document id — \"tool:{name}\", \"resource:{uri}\", or \"signal:{market}:{symbol}\" (market: crypto / kr_stock / us_stock)"

AddedJul 7, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Annotations already declare readOnly/openWorld/idempotent, but the description adds real behavioral context beyond them: uncovered resource uris return description-only text with no fabricated data, and `text` is a JSON document for resource/signal ids. The only weak spot is that the output-envelope listing partly restates what the existing output schema already provides.

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?

Front-loaded with labeled sections (Purpose / Namespaces / Triggers / When to call / Prerequisites / Next steps / Caveats / Output), which makes it scannable despite its length. Some output-envelope detail duplicates structured data and could be trimmed, but nearly every line carries routing or behavioral value.

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 single-parameter fetch tool with an output schema and full annotations, the description covers purpose, id namespaces, triggers, prerequisites, follow-up tools, and data-fidelity caveats. Nothing an agent needs in order to invoke it correctly 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 100%, so the baseline is 3, but the description adds genuine meaning by explaining what each namespace's id actually resolves to (`tool:{name}` → full docs, `resource:{uri}` → live data, `signal:{market}:{symbol}` → latest combined signal) and notes core resources are resolved server-side.

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 (fetch document by id) and immediately distinguishes itself from the sibling `search` by noting it operates on search-result ids. It also enumerates the three id namespaces (`tool:`, `resource:`, `signal:`), so an agent can tell exactly what kind of document this returns 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 Guidelines5/5

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

Explicitly says when to call ('whenever the full content behind a search result id is needed'), who calls it (ChatGPT connectors / Deep Research after `search`), the alternative path for clients without MCP resource support, prerequisites (a valid id), and next steps (tools/call, get_signal_detail, explain_decision). This is a complete routing guide to sibling tools.

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

All OneQAZ Trading Intelligence 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.