Skip to main content
Glama
romaco-labs

@romaco/mcp

Official
by romaco-labs

romaco_detect_patterns

Scan candle data to detect classical chart patterns including head and shoulders, double tops, triangles, flags, wedges, and Fibonacci harmonics, returning confidence and target prices.

Instructions

Scan the currently loaded candle data for classical chart patterns: Head & Shoulders (and inverse), Double/Triple Top/Bottom (M/W — ATR-gated alignment + depth, no range-chop false positives), Ascending/Descending/Symmetric Triangles, Bull/Bear Flags, Parallel Channels (up/down/flat — strict gates: parallel fit, 5+ touches, close containment), Rising/Falling Wedges, Cup & Handle, Rounding Bottom (parabolic basin, no handle required), unfilled momentum Gaps (≥0.5×ATR, gap_up/gap_down), and Fibonacci harmonics: ABCD, Gartley, Bat, Butterfly, Crab (strict ratio gates ±0.05 — the math fits or no pattern is reported). Each hit returns kind, confidence (0..1), target_price, invalidation_price, and anchor_count. Zombie patterns are discarded: if any candle after a pattern completed already breached its invalidation level or tagged its target, the setup is consumed and never reported — even when the current price drifted back into the live band. Cost: compressed by default (<2 KB). Set acknowledgeHighTokenCost:true to receive the full anchor points[] for each hit (≈3× larger). Call romaco_load_candles first. To draw a detected pattern on the chart, offer romaco_draw_pattern.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
acknowledgeHighTokenCostNoWARNING: setting this true includes the full points[] array (timestamp + price + role) for every detected pattern. Only opt in when the USER has explicitly asked for the exact anchor coordinates (e.g. to draw the pattern on the chart). Default (omit) returns trimmed hits without points[].
Behavior5/5

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

With no annotations, the description fully details behavioral traits: returns fields (kind, confidence, etc.), zombie pattern discarding logic, and cost implications of acknowledgeHighTokenCost. This is comprehensive.

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?

The description is detailed but front-loaded with patterns. Some redundancy could be trimmed, but it earns its length with necessary technical details.

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?

Despite no output schema, the description explains return fields, zombie pattern behavior, prerequisites, and cost tradeoffs. It is fully complete for an AI agent.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The single parameter has 100% schema coverage and the description adds context about token cost and when to set it, going beyond the schema.

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?

The description clearly states it scans candle data for classical chart patterns, listing specific pattern types. It uses a specific verb 'detect' and resource 'candle data', distinguishing it from siblings like romaco_find_levels or romaco_get_indicator_values.

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?

It provides clear prerequisites ('Call romaco_load_candles first') and a follow-up action ('To draw a detected pattern, offer romaco_draw_pattern'). It does not explicitly state when not to use it, but the context is strong.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/romaco-labs/romaco-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server