artifact-gauge-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ARTIFACT_GAUGE_ROOT | No | Root boundary for scanning local paths. If set, restricts artifact inspection to this directory. |
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 |
|---|---|
| inspect_artifactsA | Inspect local artifact sizes, extension totals, largest files, and dependency manifest names without returning file contents. |
| inspect_manifestA | Inspect bounded metadata for one recognized local dependency manifest without returning its contents or versions. |
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 2 tools
Both tools involve inspection, but inspect_artifacts provides a broad overview of artifact sizes and extensions, while inspect_manifest targets a single dependency manifest. The scope difference is clear, though the shared 'inspect' prefix could cause minor confusion.
Both tools use a consistent verb_noun pattern (inspect_artifacts, inspect_manifest), making their purposes predictable and the naming style uniform.
With only two tools, the server feels minimal and borderline for a meaningful tool set. However, the two tools cover different granularities, making the count somewhat reasonable for a focused inspection-only purpose.
The tools cover the main inspection needs: a high-level artifact overview and detailed single-manifest metadata. There may be gaps like per-file detail inspection, but within the stated non-invasive inspection scope, the surface is fairly complete.