Skip to main content
Glama

Sitesy Website Intelligence

Domain profile

domain_profile
Read-onlyIdempotent

Registration basics, a DNS summary, and subdomains drawn from public certificate logs for one domain. Costs 0.01 USDC per call. The caller pays per call in USDC on Base through x402: the first call returns the payment requirements, and an x402 aware MCP client signs and retries 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_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainYesA domain name, for example example.com

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, open-world, non-destructive behavior; the description adds material context beyond that: the 0.01 USDC per-call cost, Base/x402 payment requirement, first-call payment-requirements response, and automatic sign-and-retry behavior for an x402-aware client. It also discloses data sources (registration, DNS, public certificate logs). It does not describe response shape or freshness, but with annotations covering the safety profile this is strong.

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 front-loaded sentences: outputs and scope first, then cost, then payment mechanics. There is no redundant restatement of the schema or annotations, and the payment sentence is dense but necessary. The description is appropriately sized for the tool.

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 composite read-only tool with one required parameter and no output schema, the description identifies the three returned data groups and the nonstandard x402 payment flow, which is the main hidden complexity. It stops short of specifying output field details or data freshness, so it is not fully complete.

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?

The only parameter is domain, and schema description coverage is 100% with the schema already stating it is a domain name such as example.com. The description only reinforces 'for one domain' and does not add format, normalization, or validation semantics. Baseline 3 is appropriate when the schema fully documents the parameter.

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 the composite outputs (registration basics, DNS summary, and certificate-log subdomains) and confines the tool to one domain, so the resource and scope are clear. It does not explicitly distinguish itself from sibling DNS tools such as dns_lookup or dns_posture, so it falls short of a 5.

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

Usage Guidelines2/5

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

Gives no explicit when-to-use or when-not-to-use guidance relative to dns_lookup, dns_posture, site_check, or website_intelligence. The payment prerequisite is described, but the agent gets only implicit scope ('for one domain') rather than routing guidance.

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