Skip to main content
Glama

Create Website Monitor

hudu_create_website

Create a website monitor that polls a host for uptime, TLS expiry, WHOIS registration, and DNS changes, and alerts the owning company when checks fail.

Instructions

Create a website monitor. A website in Hudu is a live monitor, not a documentation page: Hudu polls the host on a schedule and records its uptime, TLS certificate expiry, WHOIS registration and DNS records against the owning company.

This is not a passive documentation record. From the moment it is created, the Hudu instance begins making repeated outbound requests to the host you name — HTTP polling plus TLS, WHOIS and DNS lookups — on Hudu's own schedule, and will raise alerts against the owning company when they fail. Point it only at hosts the customer actually owns or is contracted to watch, and use disable_ssl, disable_whois and disable_dns to turn off individual checks that would only produce noise. paused: true creates the record with every check dormant.

Hudu publishes no success response for this endpoint, so the created record may come back empty even though the write succeeded. When that happens this tool returns website: null — confirm with hudu_list_websites filtered by name rather than retrying, which would create a second monitor. Hudu answers 422 with the offending field named when validation fails.

Operation class: Create. Impact: Starts recurring outbound monitoring of an external host from the Hudu instance, and arms the alerts that go with it.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesThe site to monitor, written as its URL — "https://portal.contoso.com". This is the host Hudu will begin polling, and it doubles as the display name of the record.
notesNoFree-text notes shown on the website record, e.g. who owns the domain renewal.
pausedNotrue suspends monitoring of this host entirely — no uptime, TLS, WHOIS or DNS checks run and no alerts fire — while keeping the record and its history. This is the right setting for a planned outage or a decommissioning in progress; deleting the record throws away the history as well.
company_idNoNumeric id of the company this monitor belongs to, so its results appear on that company's page. Resolve a customer name to an id with hudu_list_companies first. The list endpoint has no company filter, so a website that is filed under the wrong company is awkward to find again.
disable_dnsNotrue stops DNS record monitoring, so Hudu no longer snapshots the domain's records or reports when they change. Uptime checking continues.
disable_sslNotrue stops TLS certificate monitoring, so Hudu no longer tracks the host's certificate or warns before it expires. Uptime checking continues. Set this for hosts served over plain HTTP or behind a certificate Hudu cannot validate, where the check would only produce noise.
disable_whoisNotrue stops WHOIS monitoring, so Hudu no longer tracks the domain registration or warns before the domain expires. Uptime checking continues. Set this for hosts on a domain the customer does not own, or on a TLD whose registry does not answer WHOIS.
Behavior5/5

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

The description thoroughly discloses the tool's side effects: it starts recurring outbound HTTP polling plus TLS, WHOIS, and DNS lookups, and arms alerts against the owning company. It also reveals unusual behavioral traits such as the lack of a success response returning `website: null`, the risk of duplicate monitors on retry, and 422 validation errors stating the offending field—details far beyond 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is well-structured and front-loaded: it opens with the core purpose, then explains what a website monitor is, its side effects, usage cautions, response quirks, and operation class. Every sentence contributes critical information without redundancy, making it appropriately sized for a complex operation.

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, the description adequately explains the return behavior (`website: null` on success, 422 with field on validation failure) and how to verify creation via `hudu_list_websites`. It covers side effects, parameter usage, and error handling, making it complete for an agent to select and invoke the tool correctly.

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?

The schema already provides 100% parameter descriptions, giving a baseline of 3. The description adds meaning by showing how the disable flags interact with each other and when to use `paused: true`, and it warns against setting checks that produce noise. However, it does not add new meaning for `notes` or `company_id` beyond the schema's already-rich descriptions.

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 explicitly states 'Create a website monitor' and immediately differentiates it from a passive documentation page, clarifying that a website in Hudu is a live monitor with scheduling and alerts. This clearly identifies the action and resource, distinct from sibling create tools like asset, article, or password.

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

Usage Guidelines4/5

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

The description offers clear context on when to use it—point it only at hosts customers own or are contracted to watch—and explains when to set `disable_ssl`, `disable_whois`, and `disable_dns` to avoid noise. It also recommends verifying with `hudu_list_websites` instead of retrying, though it does not explicitly name alternative tools for other entity types.

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/ZenixSolutions/hudu-mcp'

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