Skip to main content
Glama

repo_run_test

Execute allowlisted test, build, lint, and check commands on local repositories, capturing exit codes, logs, and artifact screenshots in structured results.

Instructions

Run one or more allowlisted repository verification commands.

The allowlist covers test/build/lint/check profiles for common Python, Go, Node, Maven, and Gradle repositories. command_key preserves the original single-command API. command_keys runs a bounded sequential batch; the complete batch is validated before the first command starts.

Every started command returns command, exit_code, stdout, stderr, duration and truncation metadata. Timeout/output-limit termination is a structured failed result so captured evidence is not discarded.

Commands may emit MCP_IMAGE:<repository-relative-path> lines for PNG/JPEG files under the configured test artifact directory; screenshots are returned as native MCP image content.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
command_keyNo
command_keysNo
stop_on_failureNo
timeout_secondsNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
argvNo
batchNo
imagesNo
statusYes
stderrNo
stdoutNo
commandNo
resultsNo
successYes
exit_codeNo
remainingNo
requestedNo
repositoryYes
returncodeNo
command_keyNo
duration_msYes
command_kindNo
image_warningsNo
completed_countNo
requested_countNo
stop_on_failureNo
timeout_secondsNo
stderr_truncatedNo
stdout_truncatedNo
Behavior5/5

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

Even without annotations, the description fully discloses return fields ('command, exit_code, stdout, stderr, duration and truncation metadata'), timeout behavior ('structured failed result'), and the MCP_IMAGE emission mechanism. This goes beyond annotations would typically provide and prepares the agent for unusual outcomes.

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 structured with a lead sentence defining the tool, followed by parameter-specific clarifications and behavioral details. It is moderately long but every sentence earns its place, with no filler or repetition.

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?

Given there are 4 parameters, an output schema, and no annotations, the description covers the tool's purpose, parameter options, return format, timeout behavior, and image handling. It is sufficiently complete for an agent to select and invoke 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?

With 0% schema description coverage, the description compensates by explaining `command_key` vs `command_keys` and batch validation behavior. However, it does not explicitly document `stop_on_failure` and only implicitly references `timeout_seconds` via 'timeout/output-limit termination,' so it adds value for the main parameters but leaves some to inference.

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 opens with 'Run one or more allowlisted repository verification commands,' which specifies the verb 'run' and resource 'repository verification commands.' This clearly distinguishes the tool from sibling file/git operations, as no other sibling runs commands.

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 explains the allowlist scope (test/build/lint/check for common languages) and contrasts the single-command `command_key` with the batch `command_keys`, providing clear situational usage. It doesn't explicitly state when not to use the tool, but the scope restrictions imply that arbitrary commands are not allowed.

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/cloud-Xolt/local-repo-mcp'

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