Skip to main content
Glama

Gogi

by ai.gogi.api
OverviewDiscussions(2)Admin

Analyze Chart Structure

analyze_chart_structure
Read-onlyIdempotent

Detect chart patterns and support/resistance for stocks, crypto, FX, commodities, indices, and futures. Returns technical indicators, S/R pivots, Fibonacci levels, geometric patterns, and an analysis_steps breakdown. When presenting analysis to the user, always state the key steps performed (e.g. timeframe analyzed, indicators computed, key levels identified) so the user knows what analysis was executed. Default overlay is patterns. Use get_market_data for quote + indicators.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
symbolYesTicker (AAPL, BTC-USD, EURUSD, GC, ^GSPC)
featureNoOptional overlay alias; defaults to patterns
lookbackNoOptional lookback (1W, 1M, 3M)
overlaysNopatterns (default), sr, trendline, or a named catalog overlay
timeframeNoChart window (1D, 1H, 15m, 5m, 4H, 1W)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
errorNo
messageNo
successNo

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"
+  },
+  "success": {
+    "type": "boolean"
+  }
+}
  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.1/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, open-world behavior. The description adds value beyond that by listing what is returned (indicators, S/R pivots, Fibonacci levels, geometric patterns, an analysis_steps breakdown) and by specifying overlay defaults. It does not cover latency, rate limits, or failure modes, so it is strong but not exhaustive.

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?

Purpose and asset coverage are front-loaded, and the closing recommendation to summarize analysis steps is actionable for presentation. It is slightly instruction-heavy for a tool description, but no sentence is filler.

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 values need not be explained in depth, and the description still sketches them. Combined with the annotations and full schema coverage, an agent has enough to call it correctly; only invocation-edge guidance (when not to use it, limits) is absent.

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 description coverage is 100%, so the schema already documents symbol, feature, lookback, overlays, and timeframe. The description only restates the default overlay ("Default overlay is patterns"), adding negligible meaning 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?

Specific verb ("Detect chart patterns and support/resistance") plus the resource and enumerated asset classes (stocks, crypto, FX, commodities, indices, futures). It also names the sibling it is not (get_market_data for quotes + indicators), so an agent can separate the two without opening either 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?

Names an explicit alternative and its use case ("Use get_market_data for quote + indicators"), and clarifies the default overlay, which guides invocation. It stops short of stating when this tool is the wrong choice or listing prerequisites, so it is clear context rather than full when/when-not coverage.

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