Skip to main content
Glama
minghsuy

ctscout

by minghsuy

Reverse-lookup organization for one or more domains

ctscout_lookup_domain
Read-onlyIdempotent

Identify the organization behind one or more apex domains by querying a domain-attribution warehouse built from OV/EV TLS certificates.

Instructions

Reverse-lookup ctscout.dev's domain-attribution warehouse: given one or more apex domains, return the organization(s) attributed to each.

Args:

  • domains (string[], required): apex domains to look up. Each between 3 and 253 chars. Max 10 per call. Examples: ["gs.com"], ["coalition.com", "at-bay.com"].

  • response_format ('markdown' | 'json', default 'markdown'): output format.

Returns:

  • In markdown: a table of (domain, org, cert count, subdomain count). Only domains found in the warehouse appear; missing domains indicate no attribution.

  • In JSON: the same structure as ctscout_search_company. The 'domains' array contains one entry per (domain, org) pair found.

Examples:

  • Use when: "Who owns gs.com?" -> { domains: ["gs.com"] }

  • Use when: "Are coalition.com and at-bay.com owned by the same parent?" -> { domains: ["coalition.com", "at-bay.com"] }

  • Don't use when: You have a company name and want to enumerate its domains — use ctscout_search_company instead.

Coverage caveat:

  • Returns 0 results if domain isn't in the warehouse. Either the domain is not in our index, or no OV/EV certs have been issued for it. DV-only domains (Let's Encrypt etc.) are typically not indexed.

  • When a domain IS in the warehouse but ownership is via subsidiary (e.g. an Allianz brand domain), the 'org' field shows the cert-subject organization which may differ from the brand on the homepage.

Auth & limits: same as ctscout_search_company.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
domainsYesApex domains to look up (e.g. ['gs.com', 'goldmansachs.com']). Returns the organization(s) that own each domain, plus any sibling domains in the warehouse owned by the same orgs. Max 10.
response_formatNoOutput format: 'markdown' for human-readable summary, 'json' for the raw API response.markdown
Behavior5/5

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

Adds details beyond annotations: returns 0 if domain not in warehouse, explains missing domains, cert-subject org nuance, and auth/limits. No contradiction with annotations.

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?

Well-structured with purpose, arg details, returns, examples, and caveats. Every sentence adds value, front-loaded main purpose. ~200 words, appropriately concise.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Covers return values (no output schema), edge cases, usage alternatives, and auth/limits. Complete for the tool's complexity.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, and description adds examples for domains, explains max 10, behavior of sibling domains, and return format details for both response_format options.

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?

The description clearly states it reverse-looks up organization for domains and distinguishes from sibling ctscout_search_company with explicit when-to-use examples.

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

Usage Guidelines5/5

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

Provides explicit when-to-use ('Who owns gs.com?'), when-not-to-use (company name → use search_company), and coverage caveats about DV-only domains and subsidiary ownership.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/minghsuy/ctscout-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server