launch-detector-mcp

subdomain_timeline

Read-onlyIdempotent

Track monthly new subdomains to reveal product launches, rebrands, or new regions. Bursts of hostnames expose what a company is preparing.

Instructions

New hostnames per month and the product-like names that first appeared each month. Bursts often line up with launches, rebrands or new regions.

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": "subdomain_timeline"
  }
}

Input Schema

Name	Required	Description	Default
`domain`	Yes	Company domain, e.g. 'anthropic.com' or 'stripe.com'.
`months`	No
`response_format`	No	'markdown' (default) or 'json'.	markdown

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 1, 2026

TDQS

B3.2/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is fully covered. The description adds interpretive framing about what bursts mean, but says nothing about downstream behavior (resolution, whether empty months appear, data sources). Modest added value against rich annotations.

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?

Two short sentences, front-loaded with what the tool returns. The second sentence is interpretive rather than structural but still earns its place as usage framing. No filler.

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

Completeness3/5

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

An output schema exists, so return-shape explanation is not required, and annotations carry the safety profile. However the underexplained 'months' parameter and the lack of any differentiation from the overlapping sibling tools leave an agent with real gaps when choosing between them.

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

Parameters2/5

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

At 67% schema description coverage, the description is expected to compensate for gaps. The 'months' parameter has no schema description and the description never mentions it; response_format is likewise untouched. Only 'domain' is well documented, and that comes from the schema itself, not the description.

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?

The description names a specific resource and scope: 'New hostnames per month and the product-like names that first appeared each month.' An agent can tell it produces a time-bucketed subdomain inventory. It does not differentiate itself from siblings like new_subdomains or hostname_history, so it stops 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 Guidelines3/5

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

'Bursts often line up with launches, rebrands or new regions' implies the tool is for detecting launch/rebrand activity, which is useful context. But there is no explicit when-to-use statement, no prerequisites, and no routing to the sibling tools that overlap in this space.

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

Deploy Server