Skip to main content
Glama

Nalvorn Checks

full_report

Read-only

One signed report: domain and mail, certificate, headers, crawl readiness, optional package Costs 0.01 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": {
      "url": "<url>"
    },
    "name": "full_report"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesFull URL with scheme, for example https://example.com/

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/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 materially important behavior the annotations cannot convey: a 0.01 USDC per-call cost on Base via x402, and the requirement to call over HTTP with a PAYMENT-SIGNATURE header for the tool to actually execute. It stops short of describing the failure mode when payment is absent (e.g., a 402 challenge) or settlement/refund semantics, which would have earned 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.

Conciseness3/5

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

It is short and front-loads the report contents, but the second sentence is grammatically broken — 'optional package Costs 0.01 USDC' runs two clauses together without punctuation, forcing the reader to re-parse. The payment information earns its place; the phrasing does not.

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 single-parameter, read-only, open-world tool with no output schema, the description covers the essentials an agent needs: what the report contains, what it costs, and how to authorize execution. The notable remaining gap is any indication of the response shape or size, which matters for a multi-section composite report with no output schema.

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?

With one parameter and 100% schema description coverage, the schema already explains that a full URL with scheme is required. The description adds no additional semantics about the url parameter, so the baseline of 3 applies.

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 names a specific composite artifact and enumerates its constituents (domain and mail, certificate, headers, crawl readiness, optional package), which lets an agent understand it as an aggregate report rather than a single check. It does not explicitly contrast itself with the granular siblings (tls_cert, http_headers, domain_posture), so differentiation is inferable but unstated.

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 composite nature of the report — an agent can guess this is the all-in-one option versus the per-check siblings — but there is no explicit when-to-use, when-not-to-use, or named alternative. The only hard guidance is the payment prerequisite, which is about execution rather than tool selection.

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