Skip to main content
Glama

Nalvorn Checks

openapi_conformance

Read-only

Check a live API against its OpenAPI document and list mismatches Costs 0.05 USDC per call on Base (x402). Call it over HTTP with a PAYMENT-SIGNATURE header to actually run it.

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": {
      "openapi_url": "<openapi_url>"
    },
    "name": "openapi_conformance"
  }
}

Input Schema

NameRequiredDescriptionDefault
openapi_urlYesPublic http(s) URL of an OpenAPI document to check

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations only declare readOnlyHint and openWorldHint; the description adds genuinely new behavioral facts — a 0.05 USDC charge per call on Base via x402 and the required PAYMENT-SIGNATURE header over HTTP. It omits what happens if payment is missing or rejected, and says nothing about failure modes, so it is not a 5.

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?

Two short sentences, front-loaded with the purpose before the pricing/transport caveats. The first sentence runs into the second without a separator ('mismatches Costs'), a small formatting flaw in otherwise waste-free text.

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 one-parameter, no-output-schema remote tool, the description covers purpose, cost, transport, and auth header — the essentials an agent needs to decide and invoke. It does not describe what a mismatch listing looks like or how partial payment failures surface, which keeps it from a 5.

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% for the single openapi_url parameter, so the baseline is 3. The description adds only mild context — that the document URL is the input while the 'live API' endpoint under test is implied to come from the document — but gives no URL format or reachability constraints.

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 uses a concrete verb pair ('Check ... and list mismatches') on a specific resource pair (a live API and its OpenAPI document), which is far more specific than the bare tool name. It does not explicitly contrast itself with siblings such as json_schema_strict, so it stops short of a 5.

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 the purpose (use it to test whether a deployed API matches its spec) and one precondition is stated: a PAYMENT-SIGNATURE header is needed 'to actually run it.' No when-not-to-use cases or comparisons to the sibling verification tools are given.

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