Skip to main content
Glama
mrfentmen

artifact-gauge-mcp

by mrfentmen
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Local

Server Quality Checklist

58%
Profile completionA complete profile improves this server's visibility in search results.

  • Latest release: v1.0.0

  • Disambiguation4/5

    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.

    Naming Consistency5/5

    Both tools use a consistent verb_noun pattern (inspect_artifacts, inspect_manifest), making their purposes predictable and the naming style uniform.

    Tool Count3/5

    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.

    Completeness4/5

    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.

  • Average 3.7/5 across 2 of 2 tools scored.

    See the Tool Scores section below for per-tool breakdowns.

    • No community issues in the last 6 months
    • 1 commit in the last 12 weeks
    • No stable releases found
    • No critical vulnerability alerts
    • No high-severity vulnerability alerts
    • No code scanning findings
    • CI status not available

  • Add a LICENSE file by following GitHub's guide. Once GitHub recognizes the license, the system will automatically detect it within a few hours.

    If the license does not appear after some time, you can manually trigger a new scan using the MCP server admin interface.

    MCP servers without a LICENSE cannot be installed.

  • This repository includes a README.md file.

  • No tool usage detected in the last 30 days. Usage tracking helps demonstrate server value.

    Tip: use the "Try in Browser" feature on the server page to seed initial usage.

  • Add a glama.json file to provide metadata about your server.

  • If you are the author, simply .

    If the server belongs to an organization, first add glama.json to the root of your repository:

    {
  "$schema": "https://glama.ai/mcp/schemas/server.json",
  "maintainers": [
    "your-github-username"
  ]
}

    Then . Browse examples.

  • Add related servers to improve discoverability.

How to sync the server with GitHub?

Servers are automatically synced at least once per day, but you can also sync manually at any time to instantly update the server profile.

To manually sync the server, click the "Sync Server" button in the MCP server admin interface.

How is the quality score calculated?

The overall quality score combines two components: Tool Definition Quality (70%) and Server Coherence (30%).

Tool Definition Quality measures how well each tool describes itself to AI agents. Every tool is scored 1–5 across six dimensions: Purpose Clarity (25%), Usage Guidelines (20%), Behavioral Transparency (20%), Parameter Semantics (15%), Conciseness & Structure (10%), and Contextual Completeness (10%). The server-level definition quality score is calculated as 60% mean TDQS + 40% minimum TDQS, so a single poorly described tool pulls the score down.

Server Coherence evaluates how well the tools work together as a set, scoring four dimensions equally: Disambiguation (can agents tell tools apart?), Naming Consistency, Tool Count Appropriateness, and Completeness (are there gaps in the tool surface?).

Tiers are derived from the overall score: A (≥3.5), B (≥3.0), C (≥2.0), D (≥1.0), F (<1.0). B and above is considered passing.

Tool Scores

  • Behavior3/5

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

    With no annotations provided, the description carries the full burden. It discloses the key behavioral boundary: it does not return contents or versions, and it only works with 'recognized' manifests. However, it does not describe what 'bounded metadata' includes, how unrecognized manifests are handled, or any potential side effects, leaving gaps for a read-only tool.

    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 a single, tightly written sentence (17 words) that front-loads the verb and resource and includes a crucial negation. Every word contributes to the core meaning, with no redundant or extraneous content.

    Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

    Completeness2/5

    Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

    For a tool with two required parameters and no output schema or annotations, the description under-explains key aspects: it does not define 'bounded metadata,' does not elaborate on parameter usage, and does not describe the return structure. The 'recognized' qualifier also leaves ambiguity about supported manifest types. This is insufficient for an agent to invoke the tool correctly without additional context.

    Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

    Parameters2/5

    Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

    The input schema has 0% description coverage, and the description does not explain the meaning of 'project' or 'file' beyond their names. Both are required but their exact semantics (paths, IDs, formats) are unclear. The description mentions 'local dependency manifest' but does not map it to the parameters, so it fails to compensate for the schema's lack of documentation.

    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 clearly states the tool's purpose: 'Inspect bounded metadata for one recognized local dependency manifest.' It specifies a distinct verb ('inspect'), resource ('dependency manifest'), and scope ('bounded metadata'), explicitly excluding contents and versions. This differentiates it from the sibling tool 'inspect_artifacts' by resource type, making the purpose unambiguous.

    Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

    Usage Guidelines3/5

    Does the description explain when to use this tool, when not to, or what alternatives exist?

    The description implies usage context (for local dependency manifests) and a limitation ('without returning its contents or versions'), but it does not explicitly state when to choose this tool over the sibling 'inspect_artifacts' or provide exclusions. No alternatives are mentioned, so the guidance is only implicit.

    Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

  • Behavior4/5

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

    No annotations are present, so the description carries the full burden. It explicitly states 'without returning file contents', which is a key behavioral detail for safety and privacy. It also implies read-only inspection ('Inspect local artifact sizes') and scope ('local'), though it does not explicitly state lack of side effects or permission requirements.

    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 a single, concise sentence that starts with the action and lists specific outputs, with no filler or redundancy. It is well-structured for quick parsing by an AI agent.

    Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

    Completeness4/5

    Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

    For a simple tool with one parameter and no output schema, the description adequately explains what is inspected and highlights the non-content-returning behavior. It does not specify return format, but the listed outputs ('sizes, extension totals, largest files, dependency manifest names') give a reasonable picture. The sibling relationship is not addressed, but the description is sufficiently self-contained.

    Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

    Parameters3/5

    Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

    Schema coverage is 100% with the parameter description 'Local project directory; no URLs'. The tool description adds no additional parameter-specific semantics beyond confirming the local nature, so the schema already handles parameter meaning adequately.

    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 states a clear action ('Inspect') and specific resource ('local artifact sizes, extension totals, largest files, and dependency manifest names'), which distinguishes it from the sibling tool inspect_manifest by covering broader artifact metrics rather than just manifests.

    Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

    Usage Guidelines2/5

    Does the description explain when to use this tool, when not to, or what alternatives exist?

    No guidance is provided on when to use this tool versus alternatives like inspect_manifest. The description does not mention exclusions or prerequisites, leaving the agent to infer usage from the tool name and sibling context.

    Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

GitHub Badge

Glama performs regular codebase and documentation scans to:

  • Confirm that the MCP server is working as expected.
  • Confirm that there are no obvious security issues.
  • Evaluate tool definition quality.

Our badge communicates server capabilities, safety, and installation instructions.

Card Badge

artifact-gauge-mcp MCP server

Copy to your README.md:

Score Badge

artifact-gauge-mcp MCP server

Copy to your README.md:

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/mrfentmen/artifact-gauge-mcp'

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