Skip to main content
Glama

Pattern & Regime Screener

patternfetch_scan
Read-onlyIdempotent

Scan US stocks, ETFs, and crypto for tickers currently in a given regime or showing a chart/candlestick pattern, RANKED by the honest backtested base rate + 95% CI — discovery, NOT lookup. This is the screener: instead of asking about one ticker you already know, ask "which tickers right now are in an uptrend / printing a double_bottom, and which of those has the strongest historical base rate?" and get a ranked shortlist back. Precomputed daily over a curated universe (liquid US large-caps + core/sector ETFs + major crypto pairs) so it is fast and cheap. Filters (all optional): assetClass ("stock"|"crypto"|"all"), regime ("up"|"down"|"range"), pattern (e.g. "double_bottom","double_top","head_and_shoulders","bullish_engulfing","bearish_engulfing","hammer"), minLift (-1..1 in rate points, e.g. 0.02 = keep only patterns beating their OWN pattern-free baseline by >= 2pp; 0 = at or above baseline), minBaseRate (0..1, drop tickers whose top pattern base rate is below this), tf, limit. PREFER minLift over minBaseRate: a raw base rate is not comparable across bullish and bearish rows, so minBaseRate:0.55 mostly returns bullish patterns in a rising universe before any of them carries information, whereas minLift returns the ones that measurably add something. Rows with no baseline in the evidence table are excluded by any minLift (absence of a lift is not a lift of 0). Each row: {sym, tf, assetClass, regime, pattern, baseRate, ci95, n, scope, confidence, asOf} PLUS the drift-free comparison {baseline, lift, liftCi95, liftReading} — baseline is the direction-matched rate with no pattern present, lift is baseRate minus that baseline, and liftReading says whether the difference is distinguishable from zero at all ("above-baseline" | "below-baseline" | "indistinguishable-from-baseline"). Read lift, not baseRate, when comparing a bullish row against a bearish one: in a rising universe a bullish pattern starts ahead before it carries any information. Ranked by baseRate desc, then confidence desc, then narrower CI, then fresher asOf. WHEN: an agent wants to FIND candidates across the market, not analyze a named one (then call brief on the shortlist). WHEN NOT: you already have a specific ticker (use brief). Example: {"assetClass":"all","regime":"up","minLift":0.02,"limit":20}. Impersonal historical data, not investment advice; base rates are gross directional frequencies and do not guarantee future results.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tfNoOnly return signals precomputed on this bar size. Omit to consider every precomputed timeframe.
limitNoMaximum rows to return: integer in [1,500], default 50.
regimeNoOnly return tickers currently in this regime. Omit for any.
minLiftNoNumber in [-1,1], in rate points (0.02 = 2pp). Drop tickers whose top pattern does not beat its OWN pattern-free baseline by at least this much. This is the drift-free filter and the one to reach for: minBaseRate:0.55 mostly selects bullish patterns in a rising market, whereas minLift:0.02 selects patterns that actually add something. minLift:0 means "at or above baseline". Negative values are allowed. Rows whose evidence carries no baseline are always excluded — absence of a lift is not a lift of 0.
patternNoOnly return tickers whose top pattern is this one, e.g. "double_bottom", "double_top", "head_and_shoulders", "bullish_engulfing", "bearish_engulfing", "hammer".
assetClassNoRestrict the scanned universe. Default "all".
minBaseRateNoNumber in [0,1]. Drop tickers whose top pattern base rate is below this threshold. CAUTION: a raw base rate is NOT comparable across bullish and bearish rows — in a rising universe a bullish pattern clears a high threshold on drift alone, before it carries any information. Prefer minLift for an unbiased shortlist.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed4 schema fields changed
    • changedInput schema / properties / minBaseRate / description
      Previous value: -"Number in [0,1]. Drop tickers whose top pattern base rate is below this threshold."New value: +"Number in [0,1]. Drop tickers whose top pattern base rate is below this threshold. CAUTION: a raw base rate is NOT comparable across bullish and bearish rows — in a rising universe a bullish pattern clears a high threshold on drift alone, before it carries any information. Prefer minLift for an unbiased shortlist."
    • addedInput schema / properties / minBaseRate / maximum
      Added value: +1
    • addedInput schema / properties / minBaseRate / minimum
      Added value: +0
    • addedInput schema / properties / minLift
      Added value: +{
      +  "description": "Number in [-1,1], in rate points (0.02 = 2pp). Drop tickers whose top pattern does not beat its OWN pattern-free baseline by at least this much. This is the drift-free filter and the one to reach for: minBaseRate:0.55 mostly selects bullish patterns in a rising market, whereas minLift:0.02 selects patterns that actually add something. minLift:0 means \"at or above baseline\". Negative values are allowed. Rows whose evidence carries no baseline are always excluded — absence of a lift is not a lift of 0.",
      +  "maximum": 1,
      +  "minimum": -1,
      +  "type": "number"
      +}
  2. Changed6 schema fields changed
    • addedInput schema / properties / assetClass / description
      Added value: +"Restrict the scanned universe. Default \"all\"."
    • addedInput schema / properties / limit / description
      Added value: +"Maximum rows to return: integer in [1,500], default 50."
    • addedInput schema / properties / minBaseRate / description
      Added value: +"Number in [0,1]. Drop tickers whose top pattern base rate is below this threshold."
    • addedInput schema / properties / pattern / description
      Added value: +"Only return tickers whose top pattern is this one, e.g. \"double_bottom\", \"double_top\", \"head_and_shoulders\", \"bullish_engulfing\", \"bearish_engulfing\", \"hammer\"."
    • addedInput schema / properties / regime / description
      Added value: +"Only return tickers currently in this regime. Omit for any."
    • addedInput schema / properties / tf / description
      Added value: +"Only return signals precomputed on this bar size. Omit to consider every precomputed timeframe."
  3. Added

TDQS

A5/5.0
Behavior5/5

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

Annotations already indicate safe, idempotent read operation. The description goes beyond by stating it is precomputed daily over a curated universe, fast and cheap, and provides impersonal historical data not investment advice. No contradiction with annotations.

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?

The description is well-structured with bolded terms, clear sections, and efficient use of sentences. Every sentence provides unique value, and the example input helps understanding. Length is appropriate for the tool's complexity.

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 thoroughly explains the output fields (sym, tf, baseRate, ci95, etc.) and their interpretation, including the drift-free comparison fields. Context signals (0 required params, 7 optional) are well addressed.

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?

Schema coverage is 100%, but the description adds significant value for each parameter, especially minLift and minBaseRate, explaining their interpretation, caveats, and preference. It clarifies the ranking order and output field meaning.

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 the tool scans US stocks, ETFs, and crypto for tickers in a given regime or showing a pattern, ranked by backtested base rate. It explicitly distinguishes from siblings like brief (for known tickers) and provides a concrete example query.

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?

The description includes explicit 'WHEN' and 'WHEN NOT' sections, directing agents to use brief for known tickers and to prefer minLift over minBaseRate. It also explains when minBaseRate is misleading.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.7/5.0
Disambiguation5/5

Each tool has a clearly distinct purpose: analogs for historical patterns, brief for current state, capabilities for metadata, delta for changes, multi for multi-timeframe, scan for screening. No overlap in functionality.

Naming Consistency5/5

All tools follow a consistent 'patternfetch_<noun>' pattern using snake_case, making it predictable. No mixed conventions or ambiguous verbs.

Tool Count5/5

6 tools is well-scoped for a technical analysis server. Each tool earns its place, covering key operations without being excessive or insufficient.

Completeness4/5

The tool set covers core workflows: current state, multi-timeframe, scanning, historical analogs, and polling for changes. Minor gaps (e.g., no raw data endpoint) are acceptable given the server's focus on processed insights.