Skip to main content
Glama
Sign In

toolvend - utility APIs for agents

by dev.toolvend
OverviewDiscussionsAdmin

dns

DNS lookup over DoH. Common record types (A, AAAA, MX, TXT, NS, CAA, ...) as clean JSON. Paid per call: $0.005 in USDC via x402.

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

Input Schema

NameRequiredDescriptionDefault
nameYesDNS name to resolve
typeNoRecord type, default A

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • removedInput schema / additionalProperties
      Removed value: -false
  2. First observed

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the full load and does disclose the most consequential trait: this is a paid call at $0.005 USDC via x402, which an agent must know before invoking. It also names the transport (DoH) and output format. It omits payment-flow mechanics (wallet/pre-auth), rate limits, and failure behavior, so it stops short of 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.

Conciseness5/5

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

Three short sentences, zero filler, with the identity and mechanism front-loaded and the cost disclosure last. Nothing redundant or padded.

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 simple two-parameter read-only lookup with 100% schema coverage and no output schema, the description covers purpose, transport, output format, and cost. Remaining gaps are minor: no error/timeout behavior and no explanation of how the x402 payment is settled.

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 description coverage is 100% and both parameters are documented in the schema, including the full record-type enum with a stated default. The description's list of record types ('A, AAAA, MX, TXT, NS, CAA, ...') merely echoes the enum and adds no new syntax or format guidance, so baseline 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?

States a concrete verb and resource ('DNS lookup over DoH') plus the output shape ('clean JSON'), so an agent knows exactly what the tool returns. It does not explicitly distinguish itself from the nearest sibling (rdap, url-inspect), but those serve different resources, so confusion risk is low.

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 well-known semantics of a DNS lookup, but the description never says when to prefer it over siblings like rdap or url-inspect, nor any exclusions or prerequisites. There is no explicit when-to-use guidance beyond the operation name.

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

All toolvend - utility APIs for agents 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