Skip to main content
Glama

launchfiles_mcp_registry_readiness

Read-onlyIdempotent

Probe any live product URL for /llms.txt, /.well-known/mcp.json, /.well-known/mcp-registry-auth, /.well-known/agent-card.json, remote /api/mcp tools/list, official MCP Registry drift, and public companion repository status.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "url": "<url>"
    },
    "name": "launchfiles_mcp_registry_readiness"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesLive https:// product URL or domain to probe.
repository_urlNoOptional public GitHub companion repository URL to check for 200 vs 404.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnly, openWorld, idempotent and non-destructive, so the safety profile is covered. The description does add real behavioral context beyond that: it discloses that the tool performs outbound network probes against well-known paths, calls a remote /api/mcp tools/list endpoint, and compares against the official MCP Registry and a companion repo's 200 vs 404 status. It does not say how results are reported, whether a non-responding target errors or yields negatives, or anything about latency/rate considerations for seven-plus requests per call.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence with the verb and object first, followed by the probe targets. The endpoint list is dense but each item is a distinct capability, not filler; the only cost is that the run-on enumeration makes it slightly harder to scan than a short structured list would be.

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

Completeness3/5

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

With four annotations covering the safety profile and full schema coverage, the main remaining gap is output shape: the description never indicates what an agent gets back (per-artifact pass/fail, a findings list, a readiness score) despite having no output schema. For a multi-check probe tool, that leaves the agent unable to predict the response form before invoking it.

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

Parameters4/5

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

Schema description coverage is 100% and both parameters are documented in the schema (url as the live https target, repository_url as an optional GitHub companion repo checked for 200 vs 404). The description is consistent with the schema but adds little param-level meaning beyond repeating that the URL is live and the repository is optional/public, so baseline-level credit is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a specific verb ("Probe") and a concrete resource (a live product URL) and then enumerates the exact artifacts checked: /llms.txt, /.well-known/mcp.json, mcp-registry-auth, agent-card.json, remote /api/mcp tools/list, MCP Registry drift, and companion repo status. That enumeration does distinguish it from audit siblings like seo_audit or ux_audit, though it never explicitly routes against launchfiles_live_drift_check, which the "drift" mention partially overlaps.

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?

Usage is implied by "any live product URL" and the required-property url, so an agent can infer this is for deployed sites reachable over https. There is no explicit when-to-use/when-not statement, no prerequisites, and no named alternative (e.g., use live_drift_check for pure drift monitoring rather than full readiness).

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.