Gogi

Get Market Data

get_market_data

Idempotent

FMP quote + full technicals (EMAs, stoch, MACD, RSI, ADX) + chart structure (patterns, S/R, fib) for stocks/crypto/FX/commodities/indices. No broker required. Optional timeframe (default 1day). Use get_data_feed for marketplace SKUs; analyze_chart_structure for other overlays/lookbacks.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "symbol": "<symbol>"
    },
    "name": "get_market_data"
  }
}

Input Schema

Name	Required	Description	Default
`symbol`	Yes	Ticker (AAPL, BTC-USD, EURUSD, GC, ^GSPC, BTC/USD)
`timeframe`	No	Technicals + chart structure timeframe (1min, 5min, 15min, 30min, 1hour, 4hour, 1day, weekly)

Output Schema

Name	Required	Description	Default
`error`	No
`quote`	No
`message`	No
`success`	No
`technicals`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 31, 2026

changedInput schema / properties / timeframe / description

Previous value: -"Technicals timeframe (1day, 1hour, 4hour, 5min, 15min, 30min, weekly)"New value: +"Technicals + chart structure timeframe (1min, 5min, 15min, 30min, 1hour, 4hour, 1day, weekly)"

Changed2 schema fields changedSep 13, 2026

changedOutput schema / description

Previous value: -"Structured Gogi result. Error responses include error and message fields."New value: +"Structured result. Error responses include error and message."

addedOutput schema / properties

Added value: +{
+  "error": {
+    "type": "string"
+  },
+  "message": {
+    "type": "string"
+  },
+  "quote": {
+    "type": "object"
+  },
+  "success": {
+    "type": "boolean"
+  },
+  "technicals": {
+    "type": "object"
+  }
+}

Changed1 schema field changedSep 13, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "description": "Structured Gogi result. Error responses include error and message fields.",
+  "type": "object"
+}

First observedSep 13, 2026

TDQS

A4.3/5.0

Behavior4/5

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

'No broker required' is a genuine auth/prerequisite disclosure that annotations do not express, and the default timeframe (1day) is stated behaviorally. With annotations already covering openWorld/idempotent/destructive profile, the bar is lower. Gaps: no mention of data latency/freshness or rate limits for an external FMP-backed call, which matters for a tool flagged openWorldHint=true.

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?

Three sentences, front-loaded with what you get, then routing, then parameter behavior — no filler. The acronym stack ('EMAs, stoch, MACD, RSI, ADX') is dense but each item earns its place by telling the agent what is returned.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return-value explanation is correctly omitted, and the description still enumerates the content families the agent can expect. Asset-class breadth and the no-broker prerequisite round it out. Minor gap: nothing on data delay/freshness or failure behavior when a symbol is unsupported.

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; the description adds that timeframe governs BOTH the technicals and the chart structure and that it defaults to 1day, which is meaning the schema text only partially conveys. Symbol format examples live entirely in the schema and are correctly not repeated.

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 (fetch quote) plus the exact resource bundle (technicals: EMAs, stoch, MACD, RSI, ADX; chart structure: patterns, S/R, fib) and the asset classes covered. It also names the two siblings it is not (get_data_feed, analyze_chart_structure), so an agent can disambiguate 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 Guidelines4/5

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

Explicitly routes two adjacent cases: 'Use get_data_feed for marketplace SKUs; analyze_chart_structure for other overlays/lookbacks.' That is clear context plus exclusions for the nearest siblings. It does not address other plausible alternatives (e.g., execute_prediction or data already on get_portfolio), but the ambiguity that matters most is resolved.

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

All Gogi 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.

Resources

Need Help?