Skip to main content
Glama

docs_search

Search FLOX documentation to find how-to guides, reference pages, tutorials, and explanations for behavior, configuration, and APIs.

Instructions

Top-k full-text search over the FLOX documentation (how-to guides, reference pages, tutorials, error codes, bindings overviews, explanations). Use this to ground answers about FLOX behavior, configuration, or APIs in the actual docs instead of relying on training data — call it whenever the user asks 'how do I X' / 'what does Y do' / 'where is Z documented'. The index is built from a strict allowlist; private tracker / strategy / author files are NEVER indexed.

Query syntax: plain word lists are AND-matched (every token must appear). Wrap a phrase in double quotes for exact match: "walk forward". FTS5 operators (OR, NEAR, *, parens) pass through.

Canonical workflow queries (run these instead of guessing the canonical path from training data): • User wants to record market data → docs_search('record tape'). Covers live capture and the ccxt.fetch_ohlcv historical-backfill pattern. • User asks 'how should I structure a flox project' → docs_search('project layout'). • User mentions an exchange / live data → docs_search('ccxt'). • User wants to backtest a strategy on a recorded tape → docs_search('backtest'). • User mentions strategy traces, signals, or .floxrundocs_search('floxrun').

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesFree-text query. Plain word lists are AND-matched. Wrap a phrase in double quotes for exact match.
kNoNumber of results to return (1..25). Default 5.
Behavior4/5

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

Discloses that the index is from a strict allowlist and private files are never indexed. Describes query syntax and FTS5 operators. No annotations exist, so description carries full burden. Could mention rate limits or response behavior.

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?

Well-structured with purpose, syntax, and canonical workflow sections. Front-loaded with key purpose. Slightly long but all sentences add value.

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?

Covers usage and query syntax well, but lacks description of output (no output schema). For a simple search tool with two parameters, it is fairly complete, but missing response format details.

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%, so baseline is 3. The description adds significant value beyond schema by explaining query syntax and providing example queries, particularly for the 'query' parameter.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states it performs top-k full-text search over FLOX documentation and lists documentation types. While it doesn't explicitly differentiate from siblings, the context of siblings (all specific actions) makes this the only search tool.

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?

Provides explicit when-to-use guidance (user asks 'how do I X' etc.) and includes canonical workflow queries for common tasks. However, it does not mention when not to use or 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/FLOX-Foundation/flox'

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