Skip to main content
Glama

OneQAZ Trading Intelligence

by io.github.wnsod
OverviewDiscussionsAdmin

search

Read-onlyIdempotent

Purpose: ChatGPT-connector-standard discovery search over OneQAZ's live surface — tools, resources, and the latest strong combined signals across crypto / kr_stock / us_stock. Returns result ids consumable by the fetch tool. Triggers: ChatGPT connectors and Deep Research call this automatically for any user query routed to OneQAZ ("bitcoin signal", "prediction accuracy", "korean stocks today", ...). Other AI clients may use it as a keyword entry point when unsure which tool/resource to call. When to call: first step of connector-style discovery. MCP-native clients can instead browse tools/list + resources/list directly. Prerequisites: none. Next steps: pass any result id to fetch for the full document. Caveats: corpus is rebuilt at most every 10 minutes (tool/resource catalog + top-20 strong signals per market). Empty results list means no match. Output: {results: [{id, title, url}], disclaimer, is_investment_advice, data_classification} — flat envelope, OpenAI fixed shape.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesfree-text search string (English/Korean, symbols like BTC/AAPL)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedOutput schema / description
      Added value: +"`full_data` for search — 실응답에서 추출(2026-09-23)."
    • addedOutput schema / properties
      Added value: +{
+  "results": {
+    "items": {},
+    "type": "array"
+  }
+}
  2. Changed1 schema field changed
    • addedInput schema / properties / query / description
      Added value: +"free-text search string (English/Korean, symbols like BTC/AAPL)"
  3. Added

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the readOnly/openWorld/idempotent annotations, the description adds concrete behavior: the corpus is 'rebuilt at most every 10 minutes', empty results mean no match, and the output envelope includes disclaimer/is_investment_advice/data_classification. It also states that results are ids for `fetch`, clarifying the tool's role in a multi-step workflow.

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?

The description is well-structured with labeled sections and front-loaded purpose. Most content earns its place, especially the caveats and next-step guidance. It is slightly verbose with some overlap between 'Triggers' and 'When to call', but the redundancy is mild and the labels make it easily parseable.

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 one-parameter search tool with rich annotations and an output schema, the description covers purpose, triggers, alternatives, prerequisites, next steps, freshness caveats, and result interpretation. Nothing an agent needs to decide whether to call it or how to interpret an empty result is 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%, and the query parameter is already described as a free-text string supporting English/Korean and symbols like BTC/AAPL. The description adds context about what gets searched (tools, resources, signals) and gives example queries, but it does not materially expand the parameter semantics beyond the schema. Baseline 3 is appropriate.

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?

The description states a specific verb and resource: 'discovery search over OneQAZ's live surface — tools, resources, and the latest strong combined signals across crypto / kr_stock / us_stock.' It also clarifies the return contract ('result ids consumable by the fetch tool') and distinguishes itself from sibling tools by positioning search as the entry point while fetch retrieves full documents.

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?

The description explicitly says when to call it: 'first step of connector-style discovery' and 'keyword entry point when unsure which tool/resource to call.' It also names alternatives: MCP-native clients can 'browse tools/list + resources/list directly', and result ids should be passed to `fetch`. This gives an agent clear routing guidance.

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 toolsInspect
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