Skip to main content
Glama
Sign In

Toolcall

by click.toolcall
OverviewDiscussionsAdmin

domain-check

Due-diligence check on any domain: registration age via RDAP, registrar, DNS posture (A/MX/NS), SPF and DMARC presence, SSL certificate history, and risk flags like newly-registered or no-mail-setup. One call, one JSON verdict. [Paid: $0.008 USDC per call via x402 on Base; the calling client pays automatically.]

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": "domain-check"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainYesDomain to check, e.g. example.com

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Discloses cost and payment method ($0.008 USDC via x402) which is a key behavioral trait. No annotations exist, so description covers most relevant aspects, though rate limits or error handling not mentioned.

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?

Concise: three sentences cover purpose, output format, and cost. No superfluous words. Front-loaded with key capabilities.

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 tool with one parameter and no annotations, description covers purpose, checks, output format, and cost. Missing details like error handling or response structure, but not critical for selection.

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?

Single parameter 'domain' with schema description. Schema coverage is 100%, so description adds minimal extra value (example only). Baseline 3 is appropriate.

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?

Description clearly states it performs due-diligence checks on domains, listing specific checks (registration age, DNS, SPF/DMARC, SSL, risk flags). Differentiates from siblings, none of which cover domain analysis.

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 says 'One call, one JSON verdict' indicating simplicity. No explicit when-not or alternatives, but sibling tools are unrelated, so context is clear.

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

All Toolcall 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