Skip to main content
Glama

mcp_manifest_lint

Validates MCP registry server.json and host configs against official schema, checking names, versions, packages, transports, env vars, and hard-coded secrets. Submit inline JSON or a URL.

Instructions

MCP manifest linter: validates an MCP registry server.json (official schema 2025-12-11: reverse-DNS name, 100-char description, pinned versions, packages registryType/transport, remotes, env vars, isSecret, fileSha256, additionalProperties) or a host config (mcpServers/servers: command vs url, args, env, hard-coded secrets). Inline JSON or URL. Costs 0.002 USDC on Base per successful call (x402). Without a payment key this tool returns the 402 challenge.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "mcp_manifest_lint"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNoURL of server.json or config
kindNoserver_json or host_config (auto-detected)
manifestNoInline server.json or host config (POST)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.0

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations, the description carries behavior itself and does well on the two highest-risk facts: cost (0.002 USDC on Base per successful call, x402) and auth failure mode (returns a 402 challenge without a payment key). It also notes kind auto-detection. The notable gap is return shape — it never says whether output is a pass/fail plus issue list, which matters since there is no output schema.

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?

Purpose is front-loaded in the first clause and the payment caveat is a tight standalone sentence. The parenthetical checklist of validated fields is long and partly enumerative detail, but each item does help an agent predict whether its manifest will pass.

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 no-annotation, no-output-schema, three-parameter tool, the description covers input modes, scope of validation, cost, and auth behavior. What is missing is the response shape and any limits (size, timeout, retry after 402), which an agent needs to interpret results.

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 description coverage is 100%, so all three parameters are already documented, giving a baseline of 3. The description echoes 'Inline JSON or URL' and auto-detection of kind, which is consistent but adds little beyond what the schema fields already state.

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?

States a specific verb (validates) and two concrete resources (MCP registry server.json per schema 2025-12-11, and host config with mcpServers/servers), then enumerates the checks performed. This is detailed enough to separate it from generic validators like json_schema_validate or openapi_lint without opening the schema.

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 only implied by the resource name (lint an MCP manifest before publishing) and by the 'Inline JSON or URL' input modes. There is no explicit when-to-use vs. openapi_lint or json_schema_validate, and no when-not guidance, though the input-mode sentence does tell the agent how to feed data in.

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