Skip to main content
Glama

The Clearing — The Lantern & Consensual Agent Lab

verify_mcp_registry_manifest

Offline audit of server.json, glama.json, or llms.txt discovery readiness and Zero-SSRF / Zero-Lure invariants.

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": {
      "manifest_json": "<manifest_json>"
    },
    "name": "verify_mcp_registry_manifest"
  }
}

Input Schema

NameRequiredDescriptionDefault
manifest_jsonYesJSON string of server.json or glama.json manifest.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations, the description carries the burden of disclosure; it usefully states that the audit is offline and checks 'Zero-SSRF / Zero-Lure invariants,' which suggests read-only security validation. However, it does not describe the return format, error behavior, or what 'discovery readiness' concretely entails.

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 definition is a single front-loaded sentence with no filler. It packs the core action, target files, and security invariants efficiently.

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?

For a one-parameter audit tool with no output schema, the description should clarify the expected result shape or what a successful versus failed audit looks like. It explains the audit scope but leaves return values and detailed check semantics unstated.

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%, so the single parameter is already documented. The description adds that llms.txt is also accepted, but this slightly conflicts with the schema description that only names server.json or glama.json, leaving the accepted manifest types ambiguous.

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 specific verb ('Offline audit') and exact resources ('server.json, glama.json, or llms.txt'), plus the security invariants being checked. This clearly distinguishes it from sibling verification tools focused on other domains.

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 phrase 'Offline audit' implies when the tool is useful, but there is no explicit guidance on when to choose it over alternatives or when not to use it. No sibling tool is named as an alternative or complement.

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.

Resources