Skip to main content
Glama

find_venv

Locate the python binary of a virtual environment in the current directory. Checks .venv, venv, and env folders to return a path for use with run_python_in_venv.

Instructions

Locate a virtual environment in the REPL's current directory.

    Checks, in order: .venv/, venv/, env/. Returns the path to the
    python binary if found, so it can be fed directly to
    run_python_in_venv.

    Args:
        repl_id: REPL whose cwd to search under.
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
repl_idYes
Behavior4/5

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

No annotations are provided, but the description clearly discloses the search order and return value. It does not mention side effects, but since the tool is read-only and non-destructive, the description is adequate.

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 front-loaded, with no wasted words. It uses three sentences to convey purpose, behavior, and parameter semantics efficiently.

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?

The tool is simple with one parameter and no nested objects. The description covers the return value and how it relates to run_python_in_venv, making it sufficiently complete for its complexity.

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 0%, so the description must compensate. It explains that repl_id is the REPL whose cwd to search under, adding meaning beyond the schema's 'Repl Id' label. However, it does not provide additional details like expected format or examples.

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 explicitly states the tool locates a virtual environment, specifies the search order (.venv/, venv/, env/), and explains it returns the python binary path. It also mentions the output can be fed to run_python_in_venv, distinguishing it from sibling tools.

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 implies usage by stating the search order and linking to run_python_in_venv, providing clear context for when to use it. However, it does not explicitly exclude alternative tools like run_python_in_repl or mention when not to use it.

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/angrysky56/local-repl-mcp'

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