Skip to main content
Glama
Sign In

TunnelMind Data API

by ai.tunnelmind
OverviewDiscussionsAdmin

get_domain

Returns the complete surveillance intelligence record for a domain name. If the domain is in TunnelMind's tracker database (80,000+ entries), the response includes tracker category, risk score, fingerprinting data, cookie persistence, IAB TCF purposes, and the owning corporate entity. If the domain is not in the database, a live probe is automatically run: RDAP registration data, DNS records (MX, SPF, TXT verification tokens), HTTP headers, and CSP third-party actors are fetched fresh from the edge and returned.

Use this tool when:

  • You need to know whether a specific domain tracks users, and how aggressively.

  • You are researching who owns a domain and what corporate entity controls it.

  • You want to check HTTP security headers and third-party services embedded in a site.

  • You are building a risk score for a domain before routing traffic through it.

Do NOT use this tool when:

  • You want to search by keyword or category — use search instead.

  • You want all domains for an entity — use get_entity instead.

Inputs:

  • domain (path, required): Domain name. Strip www. prefix — it is removed automatically. Subdomains are resolved to the parent: ads.doubleclick.net → doubleclick.net. Examples: doubleclick.net, google-analytics.com, intercom.io.

Returns:

  • Full DomainRecord. Free tier returns the domain, category, score, prevalence, and entity name. Pro/enterprise additionally return tcf_vendor_id, tcf_purposes, tcf_features, and disconnect_cats.

  • If the domain is not in the tracker database, live_lookup: true is set and RDAP/DNS/HTTP probe results are returned instead of tracker fields.

  • 404 if the domain cannot be found via live probe either (unknown TLD, unreachable).

Cost:

  • Anonymous (no key): 10/min, 100/day. Free key: 50/day. Pro/enterprise: included in plan.

Latency:

  • Database hit: typical <100ms, p99 <300ms.

  • Live probe: typical 2-5s, p99 10s (external DNS/HTTP calls).

Input Schema

NameRequiredDescriptionDefault
domainYesDomain name to look up (www. prefix stripped automatically)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A5/5.0
Behavior5/5

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

No annotations are provided, so the description carries the full burden and does so richly: it discloses the tracker-database-vs-live-probe branching, the automatic probe fallback, edge-fetched RDAP/DNS/HTTP behavior, tier-gated fields, 404 conditions, rate limits per tier, and typical/p99 latency including the much slower live-probe path.

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 front-loaded with the core action first, then clearly labeled blocks (Use/Do NOT/Inputs/Returns/Cost/Latency). Despite its length every section delivers information an agent needs — tier gating, fallback behavior, and rate limits are all decision-relevant.

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?

With no output schema and no annotations, the description fully compensates: it enumerates returned fields by tier, explains the live_lookup flag and what replaces tracker fields on a miss, and gives the 404 failure mode. Nothing needed to call this correctly is missing.

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 only one parameter exists, yet the description adds real semantics beyond the schema: subdomain resolution to the parent ("ads.doubleclick.net → doubleclick.net") and worked examples. This is normalization behavior an agent cannot infer from the schema at all.

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 complete surveillance intelligence record for a domain name") and distinguishes itself from siblings by naming `search` and `get_entity` as different entry points. An agent knows exactly what it retrieves without opening the schema.

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 an explicit "Use this tool when" list with four concrete scenarios and a "Do NOT use" list that routes to `search` (keyword/category) and `get_entity` (all domains for an entity). This is textbook when/when-not/alternatives guidance.

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

All TunnelMind Data API 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