Skip to main content
Glama

Visibility Genies

Get a Whois record

get_whois

Reads a domain's Whois record: when it was registered and changed, when it expires, its registrar and status codes, when Visibility Genies first saw it, and its referring domains and backlinks. Estimated price: ~$0.25, one Whois lookup. A record saved within 30 days is read free, and it opens free on Domain Overview. Each call may spend up to the workspace's agent spend limit ($2.00 unless changed in Settings) without asking: it holds at most its estimate plus a margin while it runs and is charged what it bought, never more. A call whose maximum is above the limit is refused before anything is bought, with its estimate and maximum: ask the user, then call again with approvedMaxCostUsd set to the amount they approved.

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

Input Schema

NameRequiredDescriptionDefault
domainNoThe domain. Defaults to the project's own.
projectIdYesRequired. The Visibility Genies project this call works in and is billed to. Call list_projects to find one.
approvedMaxCostUsdNoThe most, in USD, the user approved for this call after seeing its estimate and maximum. Only needed after a call was refused for costing more than the workspace's agent spend limit; never set it without asking the user.

Output Schema

NameRequiredDescriptionDefault
costNo
metaNo
boughtNo
savedResultIdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Goes well beyond the annotations (openWorldHint=true, destructiveHint=false) by disclosing price (~$0.25 per lookup), the automatic spend ceiling behavior, that the hold is at most estimate plus margin and the charge never exceeds what was bought, and the exact refusal-then-approve recovery flow. This is precisely the cost/permission behavior an agent cannot infer from structured fields.

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?

Front-loads what the record contains, then layers cost, caching, and the approval escape hatch in descending order of importance; every sentence carries either a capability or a spending-safety rule, and the final sentence tells the agent the exact recovery action.

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?

With an output schema present the description needn't explain return values, and it covers billing, caching, and refusal handling thoroughly. The only gap is that it never routes the agent to a cheaper or narrower sibling when only part of the Whois data is needed.

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?

Schema coverage is 100%, so baseline is 3, but the description adds real meaning to approvedMaxCostUsd by explaining it is only set after a refusal and only with the amount the user approved, and it clarifies that domain defaults to the project's own domain. The projectId billing scope is also reinforced in prose.

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?

Names a specific verb and resource and enumerates exactly what the record contains (registration/change/expiry dates, registrar, status codes, first-seen, referring domains, backlinks), so an agent can tell it apart from backlink- or overview-style siblings. It stops short of explicitly naming which sibling to use for a subset of that data, keeping it at a clear-but-not-differentiating 4.

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?

Gives concrete operational context: a record cached within 30 days is free, the call may auto-spend up to the workspace agent limit, and an over-limit call must be refused first, then retried with user-approved approvedMaxCostUsd. That is a clear when/how-to-use story for the cost path, though it never states when to prefer a different tool.

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