Skip to main content
Glama
reflex-search

Reflex

Official

find_islands

Identify disconnected components in the static import graph, grouping files that have no imports crossing group boundaries. Useful for detecting independent modules or clusters.

Instructions

Find disconnected components (islands) in the static import graph — groups of files that have no imports crossing group boundaries. Prefer this over manual Glob + Grep cluster analysis — Reflex computes the connected components directly. Returns {pagination, results: [{island_id, size, paths: [...]}]} sorted with largest islands first by default. Default page size 200; if pagination.has_more is true, fetch the next page with offset. Use min_island_size and max_island_size to filter by component size (default: 2–500 files, or 50% of total). Only static imports are considered. On "Index not found" / "stale" error, call index_project, then retry.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sortNoSort order: 'asc' (smallest islands first) or 'desc' (largest islands first, default)
limitNoMaximum number of islands per page (default: 200)
offsetNoPagination offset (skip first N islands). Use with limit for pagination.
max_island_sizeNoMaximum files in an island to include (default: 500 or 50% of total files)
min_island_sizeNoMinimum files in an island to include (default: 2)
Behavior5/5

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

The description fully discloses key behaviors: static imports only, default sort order, default page size (200), filtering defaults (2–500 files or 50% of total), pagination mechanism, and error recovery steps. Since no annotations are provided, the description carries the full burden and excels.

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?

The description is concise and well-structured: purpose first, then usage/advantage, then output format, then pagination details, then filtering, then error handling. Every sentence adds value without redundancy.

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?

Despite having 5 optional parameters and no output schema, the description covers all critical aspects: purpose, behavior (static imports), return format, pagination, filtering defaults, and error recovery. It is self-contained and comprehensive.

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 clear parameter descriptions. The description adds semantic value by explaining default values (e.g., 'default: 2–500 files, or 50% of total'), sort behavior, and pagination usage, enhancing understanding beyond the schema alone.

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 'Find disconnected components (islands) in the static import graph' with a precise definition. It distinguishes this tool from siblings (e.g., find_circular, find_hotspots) by focusing on disconnected groups, making its purpose unmistakable.

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 advises preferring this tool over manual alternative methods and provides error-handling guidance ('call index_project, then retry'). It implicitly indicates when to use (for islands) but does not explicitly list when not to use it relative to siblings, though context is strong.

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/reflex-search/reflex'

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