Skip to main content
Glama

Gogi

by ai.gogi.api
OverviewDiscussions(2)Admin

Get Market Data

get_market_data
Idempotent

FMP market snapshot for stocks, crypto, FX, commodities, indices, and futures. Returns last price plus day OHLC, 52-week range, market cap/PE when present, profile, headlines, and compact technicals (RSI, SMA, EMA, MACD, ADX, Stoch). No broker account required. Tickers: AAPL, BTC-USD, EURUSD, GC, CL, XAUUSD, ^GSPC (slash forms like BTC/USD are accepted). Optional timeframe for technicals (default 1day). Not Marketplace SKUs — use get_data_feed for insider/congress/financials-pro. For chart patterns / S/R geometry use analyze_chart_structure.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
symbolYesTicker (AAPL, BTC-USD, EURUSD, GC, ^GSPC, BTC/USD)
timeframeNoTechnicals timeframe (1day, 1hour, 4hour, 5min, 15min, 30min, weekly)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
errorNo
quoteNo
messageNo
successNo
technicalsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • 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"
+  }
+}
  2. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "description": "Structured Gogi result. Error responses include error and message fields.",
+  "type": "object"
+}
  3. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Adds behavioral context beyond the annotations: 'No broker account required' (auth/prerequisite), the fact that technicals default to a 1day timeframe, and the exact contents returned. Slightly weakened by the tension with readOnlyHint=false, which declares a non-read-only operation for what the description presents as a pure data retrieval.

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?

Dense but well front-loaded — the snapshot purpose and asset coverage come first, then ticker syntax, then routing exclusions. Every sentence carries information; it is on the long side but not padded.

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?

With an output schema present, the description need not explain return values in detail, yet it still summarizes them; annotations cover safety and the schema covers both parameters. Nothing an agent needs to invoke this 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 value on top: the timeframe default ('default 1day') is not in the schema, and it clarifies that slash ticker forms are accepted while also listing concrete symbols per asset class.

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 and resource ('FMP market snapshot') and enumerates the covered asset classes plus the return payload. It explicitly differentiates itself from siblings by naming get_data_feed and analyze_chart_structure, so an agent can route correctly without opening any 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?

Gives explicit when-not guidance with named alternatives: 'Not Marketplace SKUs — use get_data_feed for insider/congress/financials-pro' and 'For chart patterns / S/R geometry use analyze_chart_structure.' This is the full when/when-not/alternatives pattern.

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

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