patternfetch
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PATTERNFETCH_API_KEY | Yes | API key for patternfetch |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| patternfetch_briefA | Get a token-compact market-state brief for a crypto ticker + timeframe. Returns compact candles, detected chart/candlestick patterns with geometric confidence, support/resistance levels, trend/regime, and interpreted indicators (RSI/EMA state) plus a one-line summary. WHEN: an agent needs the current technical picture of a market without dumping raw OHLCV into context (saves tokens, avoids numeric hallucination). WHEN NOT: you need order execution, portfolio advice, or non-crypto assets. Example: {"ticker":"BTC/USDT","timeframe":"4h"}. Output is impersonal market data, NOT investment advice. |
| patternfetch_deltaA | Get only what CHANGED since your last brief for a ticker+timeframe (trend flips, new patterns, RSI-state changes). WHEN: an agent polls the same market repeatedly and wants minimal tokens. Returns changed=false when nothing material changed. Impersonal data, not advice. |
| patternfetch_analogsA | Find historical windows whose shape resembles the current price action and return the FULL distribution of what followed (win-rate, median, min, max, n) over a fixed forward horizon. WHEN: an agent wants historical context for a setup. NOT a prediction, NOT a backtest of a strategy; past distribution does not guarantee future results. Impersonal data, not advice. |
| patternfetch_capabilitiesA | List supported assets, timeframes, endpoints, and limits for patternfetch. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
Each tool has a distinct purpose: patternfetch_analogs provides historical pattern matching, patternfetch_brief gives a current market summary, patternfetch_capabilities lists supported features, and patternfetch_delta reports changes since the last brief. No two tools overlap in functionality.
All tool names follow the pattern 'patternfetch_' followed by a descriptive noun (analogs, brief, capabilities, delta). The naming is uniformly lowercase with underscores, making it predictable and easy to understand.
With only 4 tools, the server is tightly scoped to its domain of pattern analysis. This number is appropriate given the focused nature of the server, providing essential functionality without unnecessary complexity.
The tools cover the full lifecycle of pattern analysis: understanding capabilities, getting a current brief, detecting changes, and retrieving historical analogs. There are no obvious gaps for the intended use case of market analysis.