PT-MCP (Paul Test Man Context Protocol)
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No 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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| analyze_codebaseC | Perform comprehensive codebase analysis including structure, dependencies, and metrics |
| enrich_contextC | Enrich codebase context with knowledge graph data from YAGO 4.5 and Schema.org annotations |
| generate_contextC | Generate context files in specified format for the codebase |
| update_contextC | Incrementally update existing context files based on code changes |
| extract_patternsC | Identify and extract architectural and coding patterns from the codebase |
| analyze_dependenciesC | Analyze and map internal and external dependencies |
| watch_projectB | Start monitoring project for changes and auto-update context |
| extract_api_surfaceB | Extract and document public API surface of the codebase |
| validate_contextC | Validate accuracy and completeness of generated context files |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Project Context | Current project context including structure, patterns, and dependencies |
| Detected Patterns | Architectural and coding patterns detected in the codebase |
| Dependency Graph | Internal and external dependency relationships |
TDQS
Scored across 9 tools
Most tools have clearly distinct purposes, such as analyze_codebase for overall analysis, enrich_context for adding external knowledge, and watch_project for monitoring changes. However, analyze_codebase and analyze_dependencies could be slightly confusing as dependencies are part of codebase analysis, but their descriptions help clarify the separation.
All tools follow a consistent verb_noun pattern with clear, descriptive names (e.g., analyze_codebase, enrich_context, extract_api_surface). There are no deviations in style or convention, making the set highly predictable and readable.
With 9 tools, the count is well-scoped for the server's purpose of codebase analysis and context management. Each tool appears to serve a specific function in the workflow, from analysis to generation and validation, without feeling excessive or insufficient.
The tool set provides complete coverage for the domain of codebase context management, including analysis (analyze_codebase, analyze_dependencies), enrichment (enrich_context), extraction (extract_api_surface, extract_patterns), generation (generate_context), updating (update_context), validation (validate_context), and monitoring (watch_project). There are no obvious gaps, and the tools support a full lifecycle from initial analysis to ongoing maintenance.