Skip to main content
Glama
hikmahtech

drwhome

by hikmahtech
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Remote

dossier_web_surface

Fetch a domain's robots.txt, sitemap.xml, and homepage metadata (title, description, OpenGraph, Twitter cards) concurrently. Use for SEO audits, content discovery, or verifying metadata before sharing.

Instructions

Snapshot a domain's public web surface: robots.txt, sitemap.xml, and the home-page metadata (title, description, OpenGraph, Twitter cards). Use for SEO audits, content discovery, or verifying metadata before sharing; for HTTP headers use dossier_headers, for redirect behavior use dossier_redirects. Fetches /, /robots.txt, and /sitemap.xml concurrently via HTTPS, 5 s each; parses with a lightweight HTML parser. Returns a composite CheckResult: {status:"ok", meta:{title, description, og, twitter}, robots, sitemapPresent} or {status:"error", reason}.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
domainYesPublic FQDN, e.g. example.com. Must be resolvable on the public internet; IPs, ports, paths, and protocol prefixes are rejected.

Tool Definition Quality

A4.8/5.0
Behavior5/5

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

Despite no annotations, the description fully discloses behavior: concurrent HTTPS fetches with 5s timeouts, lightweight HTML parser, and return structure. It covers error handling with the composite CheckResult format.

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?

The description is well-structured with a clear flow: purpose, usage, behavior, return. While each sentence adds value, it is slightly verbose but still efficient. Could be trimmed slightly for conciseness.

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?

Given the tool's moderate complexity (fetching multiple resources, concurrency, parsing) and lack of output schema, the description covers all essential aspects: what is fetched, how, and what is returned. It is complete for an agent to understand 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?

Schema coverage is 100%, so baseline is 3. The description adds constraints beyond the schema: 'must be resolvable on the public internet; IPs, ports, paths, and protocol prefixes are rejected.' This provides valuable validation guidance.

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 clearly states 'Snapshot a domain's public web surface' and lists specific resources fetched (robots.txt, sitemap.xml, home-page <head> metadata). It distinguishes from siblings by naming dossier_headers and dossier_redirects for different use cases.

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?

Explicitly tells when to use this tool ('SEO audits, content discovery, or verifying metadata before sharing') and when not to ('for HTTP headers use dossier_headers, for redirect behavior use dossier_redirects'). Provides clear context.

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/hikmahtech/drwhome'

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