Gogi

Analyze Chart Structure

analyze_chart_structure

Read-onlyIdempotent

Chart patterns, S/R, Fibonacci, and indicators. Default overlay=patterns. Summarize steps performed when presenting results. Use get_market_data for quotes.

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": "analyze_chart_structure"
  }
}

Input Schema

Name	Required	Description
`symbol`	Yes	Ticker (AAPL, BTC-USD, EURUSD, GC, ^GSPC)
`feature`	No	Optional overlay alias; defaults to patterns
`lookback`	No	Optional lookback (1W, 1M, 3M)
`overlays`	No	patterns (default), sr, trendline, or a named catalog overlay
`timeframe`	No	Chart window (1m, 5m, 15m, 30m, 1H, 4H, 1D, 1W)

Output Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 31, 2026

changedInput schema / properties / timeframe / description

Previous value: -"Chart window (1D, 1H, 15m, 5m, 4H, 1W)"New value: +"Chart window (1m, 5m, 15m, 30m, 1H, 4H, 1D, 1W)"

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"
+  },
+  "success": {
+    "type": "boolean"
+  }
+}

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

B3.4/5.0

Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, and open-world, so safety is covered. The description adds two useful behavioral notes — the default overlay and the instruction to summarize steps performed when presenting results — but says nothing about data sources, latency, or how lookback interacts with timeframe.

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?

Four short fragments, front-loaded with the analytical scope, with zero filler. Slightly clipped to the point of losing connective clarity (e.g., 'S/R' and the feature/overlays relationship), but nothing is wasted.

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

Completeness3/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 not required, and annotations cover safety. However, for a five-parameter analysis tool with two overlapping overlay parameters and timeframe/lookback interplay, the description leaves meaningful interpretive work to the agent.

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%, so all five parameters are already documented, and the description only restates the 'overlay=patterns' default. It does not clarify the apparent overlap between 'feature' and 'overlays', which are both described as overlay aliases — a real ambiguity the description could have resolved.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names the specific analytical content (chart patterns, S/R, Fibonacci, indicators), which lets an agent distinguish it from data-retrieval siblings like get_market_data. It stops short of a full verb+resource statement, relying on the tool name to supply 'analyze', but the resource is unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

It routes one case explicitly ('Use get_market_data for quotes'), which is genuinely useful sibling differentiation, but gives no guidance on when not to use it, prerequisites, or how it relates to backtest/prediction siblings that also consume chart data.

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?