Skip to main content
Glama
Sign In

IntoDNS.ai DNS & Email Security Scanner

by ai.intodns
OverviewDiscussionsAdmin

Check HTTP/3 support

check_http3
Read-onlyIdempotent

Read-only HTTP/3 + QUIC support check for a domain. Combines three signals: Alt-Svc HTTP response header advertising h3, HTTPS/SVCB DNS records advertising alpn="h3", and a live QUIC probe to UDP/443 verifying the handshake completes. Returns per-signal verdict plus an aggregate 'http3_ready' boolean. Use when validating CDN/Cloudflare HTTP/3 rollouts or auditing modern transport posture; not relevant for mail-only domains. No auth, ~2-5s due to UDP handshake timeout.

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": {
      "domain": "<domain>"
    },
    "name": "check_http3"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainYesDomain name only, e.g. example.com (no URL, path, or port)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already establish read-only, idempotent, open-world and non-destructive; the description adds material beyond that — no auth required, ~2-5s runtime driven by the UDP handshake timeout, and the exact composition of the check (Alt-Svc header, HTTPS/SVCB DNS records, live QUIC probe). This is precisely the latency and mechanism context an agent needs to budget calls.

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?

Front-loaded with purpose and mechanism, then return shape, then usage, then operational cost — a sensible ordering. It is dense with semicolon-joined clauses and runs slightly long for one tool, but no sentence is filler.

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

Completeness5/5

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

With no output schema, the description still explains the return contract: per-signal verdict plus an aggregate 'http3_ready' boolean. Combined with one fully-documented parameter and complete annotations, nothing essential is missing.

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% and the single `domain` parameter is already documented as 'Domain name only, e.g. example.com (no URL, path, or port)'. The description only reiterates 'for a domain', adding no format or constraint details the schema lacks, so baseline 3 applies.

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?

Names a specific verb and resource ('Read-only HTTP/3 + QUIC support check for a domain') and immediately decomposes it into three concrete signals. An agent can distinguish this from scan_domain or analyze_security_headers without opening either schema, since neither sibling is described as probing UDP/443 QUIC handshakes.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly scopes use: 'validating CDN/Cloudflare HTTP/3 rollouts or auditing modern transport posture' with a concrete exclusion ('not relevant for mail-only domains'). It falls short of naming a specific alternative sibling to pick instead, but the when/when-not framing is clear.

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

All IntoDNS.ai DNS & Email Security Scanner toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources