Hostlet

Make a website

make_website

Build a real website for the user's business, club, building, class or project from a sentence or two, with its own AI that answers visitors' questions. Hostlet designs the whole thing (words, layout, photos, logo) in about two minutes. It returns right away with a live card and the address; the site appears there when it is done. Ask only what you need: what they run and anything that makes it theirs (place, what they offer). Do not ask about colors or layout.

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": {
      "about": "<about>"
    },
    "name": "make_website"
  }
}

Input Schema

Name	Required	Description	Default
`name`	No	The name of the business or group, if they said it.
`about`	Yes	What they run, in their words plus any useful details they gave: e.g. "A small bakery on Maple Street in Portland. Sourdough, croissants, open Tue to Sun 7 to 3."

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 15, 2026

TDQS

A4.4/5.0

Behavior4/5

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

With no annotations, the description carries the full burden and does well on the hardest part: it discloses asynchronous behavior ('returns right away with a live card and the address; the site appears there when it is done') plus a ~two-minute build time. It does not address permissions, account requirements, or what happens to an existing site, which keeps it from a 5.

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?

It is front-loaded with the outcome, then the async return behavior, then the questioning guidance, with no filler sentences. It is dense — several clauses are packed into the long opening sentence — but every sentence earns its place.

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?

There is no output schema, and the description compensates by stating exactly what comes back (a live card and the address) and when the finished site appears. For a two-parameter asynchronous generation tool, nothing an agent needs in order to call it correctly is missing.

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% and both parameters are documented, so the baseline is 3; the description earns more by telling the agent how to populate 'about' ('what they run and anything that makes it theirs (place, what they offer)') and by explicitly excluding layout/color preferences, which meaning is not in the schema.

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 opens with a specific verb and resource: 'Build a real website for the user's business, club, building, class or project from a sentence or two,' and then names the differentiator (its own AI that answers visitors' questions). An agent can tell this is the site-creation tool versus siblings like make_ai, add_document or change_site without opening a schema.

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?

It gives clear context for use (when the user wants a business/club/project site) and explicit when-not guidance: 'Ask only what you need... Do not ask about colors or layout.' What it lacks is explicit routing to alternatives such as change_site for edits or check_site for status, so it falls short of full when/when-not/alternatives coverage.

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

All Hostlet tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?