Skip to main content
Glama
TripQi

Fast Context MCP

by TripQi

fast_context_search

Search a codebase using natural language, returning relevant file paths, line ranges, and suggested grep keywords for follow-up queries.

Instructions

AI-driven semantic code search using Windsurf's Devstral model. Searches a codebase with natural language and returns relevant file paths with line ranges, plus suggested grep keywords for follow-up searches. Parameter tuning guide:

  • tree_depth: Controls how much directory structure the remote AI sees before searching. If you get a payload/size error, REDUCE this value. If search results are too shallow (missing files in deep subdirectories), INCREASE this value.

  • max_turns: Controls how many search-execute-feedback rounds the remote AI gets. If results are incomplete or the AI didn't find enough files, INCREASE this value. If you want a quick rough answer, use 1. Response includes a [config] line showing actual parameters used — use this to decide adjustments on retry.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesNatural language search query (e.g. "where is auth handled", "database connection pool")
max_turnsNoNumber of search rounds. Each round: remote AI generates search commands → local execution → results sent back. Default 3. Use 1 for quick simple lookups. Use 4-5 for complex queries requiring deep tracing across many files. More rounds = better results but slower and uses more API quota.
tree_depthNoDirectory tree depth for the initial repo map sent to the remote AI. Default 3. Use 1-2 for huge monorepos (>5000 files) or if you get payload size errors. Use 4-6 for small projects (<200 files) where you want the AI to see deeper structure. Auto falls back to a lower depth if tree output exceeds 250KB.
max_resultsNoMaximum number of files to return. Default 10. Use a smaller value (3-5) for focused queries. Use a larger value (15-30) for broad exploration queries.
project_pathNoAbsolute path to project root. Empty = current working directory.
Behavior4/5

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

No annotations are provided, so the description carries full burden. It discloses the multi-round search-execute-feedback mechanism and the '[config] line showing actual parameters used' for retry adjustments. It does not cover error handling, but it adds meaningful behavioral context beyond the schema.

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?

Well-structured with a clear purpose statement, a bulleted parameter tuning guide, and a closing note about the config line. Every sentence earns its place, and the front-loaded purpose aids quick comprehension.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With 5 parameters, no output schema, and no annotations, the description covers purpose, tuning, and response characteristics effectively. It could be improved by explicitly stating output format or error behavior, but the content is sufficient for an agent to use the tool correctly.

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 a valuable tuning guide with diagnostic heuristics (e.g., 'If you get a payload/size error, REDUCE this value' for tree_depth) and explains the functional meaning of max_turns rounds, going beyond the schema field descriptions.

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 'AI-driven semantic code search' with specific outputs: 'relevant file paths with line ranges, plus suggested grep keywords'. This specific verb+resource combination distinguishes it from the unrelated sibling tool extract_windsurf_key.

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 actionable tuning guidance (e.g., 'If search results are too shallow... INCREASE this value') and suggests using max_turns=1 for 'quick rough answer'. However, it does not explicitly mention when not to use or alternative tools, though the sibling is unrelated and the context implies use cases.

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/TripQi/fast-context-fork'

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