Skip to main content
Glama

DNS Record Lookup Payment Quote

dns_records_quote
Read-onlyIdempotent

Returns the payment terms for https://horizonpulse.dev/api/dns/records (base $0.002; USDC on Base only); this tool never runs the check or pays. Pay the 402 over HTTP with x402 v2: GET ?name=example.com&type=A (one name, one type). DNS lookup for one name and one record type (A, AAAA, CNAME, MX, NS, TXT, SOA, CAA, SRV, PTR): answers, TTLs and response code as our resolver received them at query time. Answers can differ by resolver, location and time. No zone transfers or bulk enumeration. A resolver-confirmed NXDOMAIN or empty NODATA answer is charged. Bad input, timeout, SERVFAIL, REFUSED or resolver failure: not charged. USDC on Base only.

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": "dns_records_quote"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the readOnly/idempotent annotations, the description discloses the real behavioral surface: the charge policy (NXDOMAIN/NODATA billed; bad input, timeout, SERVFAIL, REFUSED or resolver failure not billed) and the caveat that answers vary by resolver, location and time. This is exactly the kind of billing and result-consistency context annotations cannot express.

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 and price are front-loaded in the first clause and the paragraph stays dense with substantive facts. Minor waste: 'USDC on Base only' is repeated verbatim near the end, and the semicolon run-ons make the charging rules slightly harder to scan than a short bulleted ordering would.

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?

For a zero-parameter quote tool with no output schema, the description covers everything an agent needs: what is returned, what is billed, what is not billed, scope exclusions, and result variability. Return-value explanation is not required since there is no output schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool has zero input parameters (baseline 4), yet the description still explains the semantics of the downstream request: one name, one type, with the full allowed type list (A, AAAA, CNAME, MX, NS, TXT, SOA, CAA, SRV, PTR). That adds genuine meaning about what the quoted call consumes without contradicting the empty schema.

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 opens with a precise verb+resource ('Returns the payment terms for https://horizonpulse.dev/api/dns/records') and immediately distinguishes itself from the actual lookup by stating 'this tool never runs the check or pays'. It also names the exact lookup endpoint, record types and price, so an agent can tell this is a quote/metadata tool, not the DNS query itself.

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?

It clearly states the tool's role (obtain terms; do not pay) and gives the follow-on action ('Pay the 402 over HTTP with x402 v2'), plus the request shape GET ?name=...&type=..., and explicitly excludes out-of-scope work ('No zone transfers or bulk enumeration'). What it lacks is an explicit pointer to the sibling that actually performs/pays for the call, so the agent must infer the handoff.

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.