plsql-test-mcp
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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| checkUnitTestabilityA | Analyze an IFS .plsql or .plsvc source file and determine whether each function/procedure is unit testable with pltst. Returns suggested @IgnoreUnitTest annotations when not testable. |
| annotateIgnoreUnitTestA | Insert @IgnoreUnitTest immediately before a method in a .plsql/.plsvc file. Call with confirmed=false first to preview, then confirmed=true to write. |
| generateUnitTestB | Generate or append a pltst unit test block for a testable method. Follows IFS Developer Studio pltst conventions with @MockTable/@MockPackage placeholders. |
| runUnitTestC | Prepare PL/SQL unit test execution by returning ifs-f1-codegen-dev generate_and_deploy instructions for the source + pltst files. |
| runPlsqlTestWorkflowC | End-to-end workflow: check testability → annotate if needed OR generate pltst → optionally prepare test run via ifs-f1-codegen-dev. |
| getIgnoreUnitTestRulesB | Return the catalog of supported @IgnoreUnitTest annotation reasons used in IFS. |
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 6 tools
Each tool has a distinct, non-overlapping purpose: annotation insertion, testability analysis, test generation, rule retrieval, workflow orchestration, and test execution preparation. No two tools could be confused.
All names follow a consistent camelCase verb_noun pattern, with clear verbs (annotate, check, generate, get, run) and specific nouns. The pattern is uniform and predictable.
Six tools is ideal for this domain. Each tool covers a necessary step in the testing workflow without unnecessary redundancy or gaps, making the set well-scoped.
The tools cover the entire lifecycle: checking testability, annotating non-testable methods, generating tests, retrieving rules, and preparing for execution. The workflow tool ties it together, leaving no dead ends.