Skip to main content
Glama

rlm_start

Initialize a persistent sandbox session to analyze a codebase directory based on a query, returning compact summaries and metadata.

Instructions

Start an RLM exploration session. Returns session_id, metadata, limits, and available functions. Set include_guidance=true to include strategy/example coaching text.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathYesAbsolute path to the directory to explore
queryYesWhat you want to find or analyze
max_output_charsNoMax characters per execute output
max_llm_callsNoMaximum llm_query/llm_query_batched calls for this session
max_execute_callsNoMaximum rlm_execute calls for this session
execution_timeout_secondsNoPer-rlm_execute timeout in seconds
include_guidanceNoInclude strategy/example guidance text in the response (larger payload)
include_metadataNoScan directory and include file counts/types in response (set false for faster startup)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It mentions return values (session_id, metadata, limits, functions) and the include_guidance flag, but does not disclose side effects, state creation, or access requirements for the directory path.

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 very concise: two sentences with the purpose front-loaded. No wasted words.

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?

Given an output schema exists and 8 parameters (2 required), the description adequately outlines the tool's purpose and key returns. It could be slightly more complete by mentioning the include_metadata parameter's effect, but overall sufficient.

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 the schema already documents all parameters. The description only adds context for the include_guidance parameter, which is minimal. It does not meaningfully augment the schema definitions.

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 the tool starts an RLM exploration session. It identifies the resource and action, but does not explicitly differentiate from sibling tools rlm_end and rlm_execute, which are for ending and executing within sessions.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies it's the first step in an RLM workflow, but it does not provide explicit guidance on when to use versus alternatives, nor does it mention prerequisites or when not to use.

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/stefanoshea/rlm-tools'

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