EasyPR
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| root | No | Approved directory root passed as a --root argument. At least one root is required. May be specified multiple times, or use EASYPR_ALLOWED_ROOT with ':'-separated roots instead. | |
| EASYPR_ALLOWED_ROOT | No | Approved directory root(s) for EasyPR to inspect. Separate multiple roots with ':' on Linux and macOS. At least one approved root is required, either via this variable or one or more --root arguments. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| inspect_repositoryA | Give a first overview of a repository. Returns top-level layout, important files (README, CONTRIBUTING, manifests, CI), language counts and detected project type. Read-only; nothing is executed. Args: path: Repository directory. Relative paths are resolved against the first approved root. |
| get_setup_guideA | Find how a project says it should be installed, run and tested. 'documented' items come from the README or CI config. 'inferred' hints come from file names and are unverified. No command is ever executed. Args: path: Repository directory. Relative paths are resolved against the first approved root. |
| find_relevant_codeA | Find files likely related to an issue or task, using keyword search. Each result has file path, role (source/test/docs/config), matching line numbers with snippets, and a plain-language reason. These are leads to verify, not conclusions. Args: path: Repository directory. Relative paths are resolved against the first approved root. query: The issue title/body or task description (names, features, error text). max_results: How many files to return (1-25). |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
Each tool targets a distinct output: repository overview, setup instructions, and code search. Minor overlap exists because inspect_repository and get_setup_guide both draw from README/CI files, but the intended purposes are clear enough to avoid confusion.
All tool names follow a consistent verb-first snake_case pattern (inspect_repository, get_setup_guide, find_relevant_code). No mixing of conventions or ambiguous prefixes.
Three tools is well-scoped for a read-only repository reconnaissance assistant. Each tool has a clear, non-overlapping role and the count is within the ideal 3–15 range.
The surface covers overview, setup discovery, and code search but lacks essential follow-up operations like reading a full file or viewing PR diffs/commits. For a server named EasyPR, these are notable gaps that could hinder deeper review workflows.