Skip to main content
Glama
keel-trade

Keel — Hyperliquid trading strategies

keel_components_search

Read-onlyIdempotent

Search the component catalog by keyword, semantic query, category, or pipeline position to find matching components for trading strategy construction.

Instructions

Search the Keel pipeline component catalog by keyword, semantic query, category, input/output type, or position in the pipeline (after/before). Returns compact entries (name, category, description, input/output type) for the agent to triage. Do NOT use to fetch full param schemas of one component — use keel_components_compose_help. Do NOT use to enumerate strategies — call keel_strategy_search.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
keywordNoCase-insensitive substring match against name or description. The CLI positional arg maps here — `keel components search momentum` filters to components mentioning 'momentum'. For weighted token-scoring across name/category/description, use `--query` instead.
queryNoFree-text semantic query — tokens are matched against name, category, and description with weighted scoring (name ×3, category ×2, description ×1). Returns components scored > 0 ranked by relevance. Pair with `keyword` (or the CLI positional keyword) to first narrow by substring, then rank.
categoryNoRestrict to one component category.
input_typeNoRestrict to components consuming this type (e.g. `SignalSeries`).
output_typeNoRestrict to components producing this type (e.g. `ForecastSeries`).
afterNoReturn components that can FOLLOW the named component (their input type accepts that component's output).
beforeNoReturn components that can PRECEDE the named component (their output type matches that component's input).
limitNoMaximum number of results.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true. The description adds context about return format ('compact entries (name, category, description, input/output type) for the agent to triage'), which is helpful beyond the annotations. No contradictions.

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, front-loaded with the main purpose and search dimensions, then exclusionary usage guidelines. No wasted words.

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?

Given 8 parameters with full schema coverage, an output schema, and annotations, the description covers the tool's behavior, result format, and usage boundaries completely. No gaps.

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

Parameters4/5

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

Schema coverage is 100% with good descriptions. The description adds extra value by explaining the difference between keyword and query (weighted scoring, substring vs semantic) and the purpose of the result format, enriching 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 specifies 'Search the Keel pipeline component catalog by keyword, semantic query, category, input/output type, or position in the pipeline' with a clear verb and resource, and distinguishes from siblings like keel_components_compose_help and keel_strategy_search.

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?

Explicitly states when NOT to use: 'Do NOT use to fetch full param schemas of one component — use keel_components_compose_help. Do NOT use to enumerate strategies — call keel_strategy_search.' Provides clear alternatives.

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/keel-trade/keel-trade'

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