Skip to main content
Glama

Dechonet-MCP

by com.dechonet
OverviewDiscussionsAdmin

Watch a Domain (daily re-check)

watch_domain
Idempotent

Start (or reuse) a daily DechoNet watch on a domain so that changes are recorded over time — SSL grade/issuer/expiry, DNS records, HTTP security headers, domain registration, and optionally OWASP posture and impersonation exposure. Use this once when the user cares about a domain beyond a one-off check (their own domain, a client, a vendor, a target under investigation). After this, domain_changes answers "what changed since last time?" from real daily snapshots. Not read-only (it creates a watch record) but idempotent: watching an already-watched domain returns the existing watch. No account, no email, no PII — a watch is keyed by domain+tool and its history page is a public unguessable URL you can share with the user. Rate-limited (a few watches per minute).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
toolsNoWhich checks to re-run daily. Default ['ssl','dns','http','rdap'] (certificate, DNS, security headers, registration). Add 'owasp' and/or 'impersonation' for posture and brand-exposure tracking, 'pqc' to record the day post-quantum key exchange is turned on, 'exposure' to catch a newly exposed admin screen, dev tool or staging server.
domainYesRegistered domain to watch (e.g., 'example.com'). Scheme and path are stripped.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
domainYes
failedNoTools that could not be watched (rate limit or error)
watchesYesOne entry per tool now under a daily watch
reportUrlYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / tools / description
      Previous value: -"Which checks to re-run daily. Default ['ssl','dns','http','rdap'] (certificate, DNS, security headers, registration). Add 'owasp' and/or 'impersonation' for posture and brand-exposure tracking, 'pqc' to record the day post-quantum key exchange is turned on."New value: +"Which checks to re-run daily. Default ['ssl','dns','http','rdap'] (certificate, DNS, security headers, registration). Add 'owasp' and/or 'impersonation' for posture and brand-exposure tracking, 'pqc' to record the day post-quantum key exchange is turned on, 'exposure' to catch a newly exposed admin screen, dev tool or staging server."
    • changedInput schema / properties / tools / items / enum
      Previous value: -[
-  "ssl",
-  "dns",
-  "http",
-  "rdap",
-  "owasp",
-  "impersonation",
-  "pqc"
-]New value: +[
+  "ssl",
+  "dns",
+  "http",
+  "rdap",
+  "owasp",
+  "impersonation",
+  "pqc",
+  "exposure"
+]
  2. Changed2 schema fields changed
    • changedInput schema / properties / tools / description
      Previous value: -"Which checks to re-run daily. Default ['ssl','dns','http','rdap'] (certificate, DNS, security headers, registration). Add 'owasp' and/or 'impersonation' for posture and brand-exposure tracking."New value: +"Which checks to re-run daily. Default ['ssl','dns','http','rdap'] (certificate, DNS, security headers, registration). Add 'owasp' and/or 'impersonation' for posture and brand-exposure tracking, 'pqc' to record the day post-quantum key exchange is turned on."
    • changedInput schema / properties / tools / items / enum
      Previous value: -[
-  "ssl",
-  "dns",
-  "http",
-  "rdap",
-  "owasp",
-  "impersonation"
-]New value: +[
+  "ssl",
+  "dns",
+  "http",
+  "rdap",
+  "owasp",
+  "impersonation",
+  "pqc"
+]
  3. Added

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already declare readOnlyHint=false and idempotentHint=true, but the description goes further: it explains the idempotency semantics (re-watching returns the existing watch), states no account/email/PII, that the history page is a public unguessable shareable URL, and that it is rate-limited. These are operational traits an agent could not derive from the 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?

Dense but front-loaded: the core action and the downstream tool relationship appear in the first two sentences, with constraints (no PII, rate limits) trailing. Every sentence carries information, though it is longer than strictly necessary.

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?

An output schema exists, so return values need not be described. For a 2-param tool with full schema coverage and full annotation coverage, the description's coverage of trigger, side effects, sharing, and limits is complete.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description adds genuine meaning by expanding each enum value's purpose (e.g., 'ssl' records grade/issuer/expiry, 'pqc' records the day post-quantum key exchange is enabled, 'exposure' catches newly exposed admin screens). This clarifies group intent beyond the terse enum labels.

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+resource ('start (or reuse) a daily DechoNet watch on a domain') and enumerates exactly what is tracked (SSL, DNS, headers, registration, optional OWASP/impersonation). It explicitly differentiates from the sibling domain_changes, which it frames as the downstream 'what changed?' reader.

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?

Gives an explicit trigger ('use this once when the user cares about a domain beyond a one-off check') with concrete examples (own domain, client, vendor, target), and names the alternative workflow (one-off checks vs. domain_changes afterward). No inference required.

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

All Dechonet-MCP toolsInspect
Try in Browser
Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources