Skip to main content
Glama

Gogi

by ai.gogi.api
OverviewDiscussions(2)Admin

Get Market Data

get_market_data
Idempotent

FMP quote + OHLC + compact technicals for stocks/crypto/FX/commodities/indices. No broker required. Optional timeframe (default 1day). Use get_data_feed for marketplace SKUs; analyze_chart_structure for patterns/S/R.

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.4/5.0
Behavior3/5

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

The description adds real context beyond annotations with 'No broker required' (no auth dependency) and the default timeframe. However, readOnlyHint=false combined with the openWorldHint=true on an obviously read-style tool is never reconciled, and no rate-limit or data-delay behavior is disclosed. Useful but incomplete against a non-trivial annotation profile.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three dense sentences, front-loaded with what the tool returns, then the operational note, then the sibling routing. No filler and every clause carries signal.

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?

With an output schema present, return format need not be described, and coverage of inputs, scope, and alternatives is strong. The one unresolved item is why readOnlyHint is false for a retrieval tool, which an agent deciding on side effects would want clarified.

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 the default value ('default 1day') that the schema does not state, and identifies the timeframe as controlling the technicals. That is meaningful value beyond the structured fields.

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?

Names a specific verb (get) and resource (market data), enumerates the covered asset classes (stocks/crypto/FX/commodities/indices) and the payload (FMP quote + OHLC + compact technicals). This makes it immediately distinguishable from data-plumbing siblings like get_data_feed.

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 routes the agent: 'Use get_data_feed for marketplace SKUs; analyze_chart_structure for patterns/S/R.' Two named alternatives with the conditions that select each, which is exactly the when/when-not guidance the dimension rewards.

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
Context Every Agent Can ShareAgents share what they learn, hand off work, and keep it when you switch models. Start with 5 GB free.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources