aipricepatterns

Search by Sketch

search_by_sketch

Read-onlyIdempotent

Search for historical patterns similar to a custom 'sketched' price trajectory (Sketch-to-Search). Useful when you want to find matches for a hypothetical or hand-drawn pattern.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`limit`	No	Max matches to return
`symbol`	No	Reference symbol for scale	BTCUSDT
`interval`	No	Reference interval	1h
`token_id`	No	Optional Chart access token (64-hex, same as X-Aipp-Chart / the token on /profile). After the daily free MCP quota, paid tools require the Chart $29/mo Stripe subscription. Legacy Manus token_id still works only when MCP_BILLING=manus.
`chart_token`	No	Optional Chart access token. Prefer the X-Aipp-Chart header in the MCP client config so every tool call is covered.
`queryValues`	Yes	Array of price points representing the sketched pattern (e.g. [10, 11, 10.5, 12])

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedSep 21, 2026

addedInput schema / properties / chart_token

Added value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "anyOf": [
+    {
+      "not": {}
+    },
+    {
+      "minLength": 1,
+      "type": "string"
+    }
+  ],
+  "description": "Optional Chart access token. Prefer the X-Aipp-Chart header in the MCP client config so every tool call is covered."
+}

changedInput schema / properties / token_id / description

Previous value: -"Optional Manus access token. Paid tools use tokenized service access, not a monthly subscription: when token_id is omitted the server returns payment_required with a Solana Pay invoice, and after payment you retry with the same token while the server uses Manus token/resolve to recover pending access."New value: +"Optional Chart access token (64-hex, same as X-Aipp-Chart / the token on /profile). After the daily free MCP quota, paid tools require the Chart $29/mo Stripe subscription. Legacy Manus token_id still works only when MCP_BILLING=manus."

First observedJul 6, 2026

TDQS

A3.9/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds no extra behavioral context such as auth requirements, rate limits, or response format. It is consistent with annotations and adds only the 'Sketch-to-Search' concept, which is more purpose than behavior.

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?

Two sentences with no wasted words. The action is front-loaded ('Search for historical patterns...') followed by a concise usage note. Every sentence earns its place.

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?

The tool has no output schema, and the description does not mention what it returns (e.g., matches, similarity scores, pagination). The limit parameter is also not referenced. While the purpose is clear, for a search tool the return format is an important missing piece, so completeness is moderate.

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 all parameters are already documented. The description adds no additional meaning about parameters, so the baseline of 3 applies without any extra credit.

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 verb 'search' and the resource 'historical patterns', and specifies the unique aspect of a 'sketched' price trajectory. This distinguishes it from siblings like explain_candle_match or get_candle_analogue_map, which serve different purposes.

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?

The description provides a clear usage context: 'Useful when you want to find matches for a hypothetical or hand-drawn pattern.' It does not explicitly mention alternatives or when not to use it, but the context is sufficient for an agent to infer when this tool applies.

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

All aipricepatterns 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?