Skip to main content
Glama

Company Domain Profile Payment Quote

domain_profile_quote
Read-onlyIdempotent

Returns the payment terms for https://horizonpulse.dev/api/domain/profile (base $0.05; USDC on Base only); this tool never runs the check or pays. Pay the 402 over HTTP with x402 v2: GET ?domain=vercel.com. To profile a company from its domain: name, description and logo (JSON-LD and Open Graph), company social links, tech-stack hints, email provider (MX) and SPF/DMARC, TLS certificate and security headers, llms.txt and /.well-known/x402 presence, read from its own public site and DNS. Input: one domain. Company-level only: no personal data and no WHOIS or registry fields. Obeys robots.txt. Unreachable sites are 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": "domain_profile_quote"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior5/5

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

Goes well past the annotations by disclosing price and currency/chain ('base $0.05; USDC on Base only'), the no-charge rule for unreachable sites, robots.txt compliance, and a data-scope restriction (company-level only, no personal data, no WHOIS/registry fields). Those are precisely the operational facts an agent needs before spending money.

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?

Key facts — payment-only behavior, price, currency — are front-loaded, and the feature enumeration is informative rather than filler. It is nonetheless a long semicolon-chained run-on with 'USDC on Base only' restated twice.

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 no output schema and no parameters, the description does most of the work: it explains what is returned, what is excluded, and the billing conditions. The one gap is the shape of the quote response itself (what 'payment terms' actually contains), which is left implicit.

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 schema declares zero properties, so it supplies no parameter meaning at all. The description adds 'Input: one domain' and an example value, which is useful, but because that domain belongs to the paid endpoint rather than this tool, the wording risks making an agent look for a domain argument that does not exist.

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?

States a specific verb and resource ('Returns the payment terms for <url>'), draws an explicit boundary ('this tool never runs the check or pays'), and then spells out the exact dataset the paid endpoint yields, which lets an agent separate it from sibling quotes like domain_ssl_quote or email_check_quote.

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 how-to-use context: the price, the x402 v2 payment flow (GET ?domain=vercel.com) and the fact that payment happens over HTTP rather than through the tool. It lacks explicit routing guidance to the narrower siblings (e.g. when to pick this over the SSL-only or email-only quote), so it stops short of a full when/when-not statement.

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.