Straelo Relay

Domain & Agent Discovery Check

domain_agent_discovery_check

Read-only

Inspect a public domain across DNS, HTTP/HTTPS/TLS, email posture and AI-agent discovery surfaces, including robots.txt, llms.txt, OpenAPI, MCP, x402 and Agent Card availability. USE WHEN: an agent needs a single-call observational check of a domain's surfaces or wants to compare with a previous state. DO NOT USE WHEN: protocol validation, Agent Card/A2A validation, MCP compliance validation, security certification, or a consumption guarantee. USE domain_risk_trust_decision FOR: merchant/domain trust. Operational behavior: no tool-specific auth or rate limit; remote surfaces may throttle requests.

Input Schema

Name	Required	Description	Default
`domain`	Yes	Bare public domain for consolidated domain health, DNS, TLS, and email-posture inspection; no protocol or path; localhost and IP literals are rejected.
`previous_state`	No	Optional prior `new_state` returned by this product. Supplied statelessly by the caller; when provided, it is compared against the current observation to populate `changes`. Omit it for a baseline inspection with no change detection.

Output Schema

Name	Required	Description
`dns`	Yes	Observed DNS records and diagnostics.
`domain`	Yes	Validated public domain.
`health`	Yes	Observed domain health: DNS, HTTP, HTTPS, redirects, TLS, and latency.
`issues`	Yes	Detected issues from the inspection: unresolved DNS, unavailable HTTPS, missing SPF/DMARC, TLS expiring soon, or unavailable agent-discovery signals. Each item includes a code, severity, message, and evidence references. Empty when no issues are found. Not a safety or security verdict.
`actions`	Yes	Recommended remediation actions derived from detected issues. Each item includes a code and a human-readable action. The tool does not execute these actions; they are recommendations only.
`changes`	Yes	Material field-level differences between `previous_state` and the current observation. Each item names a changed field with its previous and current values. Empty when `previous_state` is omitted or no field differs. Requires `previous_state` to produce non-empty results.
`evidence`	Yes	Observed evidence from DNS, HTTP/HTTPS, and agent-discovery checks. Each item names a source, the observation timestamp, the observed value, and freshness. Contains live remote observations; does not guarantee proof or validation.
`new_state`	Yes	Current observation state, structured identically to `current_state`. Can be supplied as `previous_state` in a subsequent call to enable change detection. Not persisted server-side; the caller stores and passes it back.
`observed_at`	Yes	UTC timestamp when the inspection observation was generated, in ISO 8601 format with Z suffix. Reflects the local observation time, not a provider timestamp.
`data_quality`	Yes	Observation quality summary: checks requested, completed, and failed, plus coverage (complete or partial). Reflects partial failures and missing surfaces. Not a score or verdict.
`current_state`	Yes	Structured snapshot of the current observation: domain, DNS, health, email posture, and agent readiness. Identical to `new_state`. Compared against `previous_state` to produce `changes` when supplied. Not persisted server-side.
`email_posture`	Yes	Observed email posture including MX, SPF, and DMARC.
`agent_readiness`	Yes	Observed agent discovery signals.
`security_posture`	Yes	Observed HTTPS/TLS security posture; not a safety verdict.

Schema Changelog

Changes observed during successful MCP inspections.

Changed9 schema fields changedNov 2, 2026

changedInput schema / properties / previous_state / description

Previous value: -"Optional prior new_state returned by this product for stateless change detection."New value: +"Optional prior `new_state` returned by this product. Supplied statelessly by the caller; when provided, it is compared against the current observation to populate `changes`. Omit it for a baseline inspection with no change detection."

addedOutput schema / properties / actions / description

Added value: +"Recommended remediation actions derived from detected issues. Each item includes a code and a human-readable action. The tool does not execute these actions; they are recommendations only."

addedOutput schema / properties / changes / description

Added value: +"Material field-level differences between `previous_state` and the current observation. Each item names a changed field with its previous and current values. Empty when `previous_state` is omitted or no field differs. Requires `previous_state` to produce non-empty results."

addedOutput schema / properties / current_state / description

Added value: +"Structured snapshot of the current observation: domain, DNS, health, email posture, and agent readiness. Identical to `new_state`. Compared against `previous_state` to produce `changes` when supplied. Not persisted server-side."

addedOutput schema / properties / data_quality / description

Added value: +"Observation quality summary: checks requested, completed, and failed, plus coverage (complete or partial). Reflects partial failures and missing surfaces. Not a score or verdict."

addedOutput schema / properties / evidence / description

Added value: +"Observed evidence from DNS, HTTP/HTTPS, and agent-discovery checks. Each item names a source, the observation timestamp, the observed value, and freshness. Contains live remote observations; does not guarantee proof or validation."

addedOutput schema / properties / issues / description

Added value: +"Detected issues from the inspection: unresolved DNS, unavailable HTTPS, missing SPF/DMARC, TLS expiring soon, or unavailable agent-discovery signals. Each item includes a code, severity, message, and evidence references. Empty when no issues are found. Not a safety or security verdict."

addedOutput schema / properties / new_state / description

Added value: +"Current observation state, structured identically to `current_state`. Can be supplied as `previous_state` in a subsequent call to enable change detection. Not persisted server-side; the caller stores and passes it back."

addedOutput schema / properties / observed_at / description

Added value: +"UTC timestamp when the inspection observation was generated, in ISO 8601 format with Z suffix. Reflects the local observation time, not a provider timestamp."

AddedNov 2, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint=true, openWorldHint=true, destructiveHint=false), and the description adds genuinely new operational context: no tool-specific auth or rate limit, but remote surfaces may throttle. It also implies observations can differ between calls, consistent with idempotentHint=false. Minor gap: it does not say what happens when a surface is unreachable, though the output schema covers return structure.

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?

Purpose sentence first, then clearly delimited USE WHEN / DO NOT USE WHEN / alternative / operational notes. Every line carries routing or constraint value; the enumeration of surfaces is long but load-bearing.

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 an output schema present, return values need no explanation, and the description covers the remaining burden: scope, exclusions, the sibling alternative, auth/rate-limit posture, and the fact that throttling can occur. Nothing an agent needs in order to call this correctly is absent.

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?

Schema coverage is 100% and both parameters are documented in the schema (domain constraints, previous_state semantics). The description only reinforces that this is a public-domain, observation-only check and that comparison requires a prior state; it adds no format or edge-case detail beyond the schema, so the baseline 3 applies.

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?

Opens with a specific verb+resource ('Inspect a public domain') and enumerates exactly which surfaces are covered (DNS, HTTP/TLS, email posture, robots.txt, llms.txt, OpenAPI, MCP, x402, Agent Card). This is clearly distinguished from the trust-oriented sibling domain_risk_trust_decision, which is named explicitly.

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?

Explicit USE WHEN (single-call observational check, or comparison against a previous state) and DO NOT USE WHEN (protocol/Agent Card/MCP validation, security certification, consumption guarantee) sections, plus a pointed redirect to domain_risk_trust_decision for merchant/domain trust. Nothing is left to inference.

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

All Straelo Relay tools Inspect

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

Need Help?