Skip to main content
Glama

nsd_publish

Put a page online at .nsd.sg. Give a site name and either the full HTML of the page or a list of files. Creates the site if you do not have it yet; on a site you already own it adds or replaces the given files and keeps the rest. Returns the live URL. IMPORTANT: if any file contains , on*= attributes or javascript:, send it as files with encoding "base64" (standard base64 of the UTF-8 text); the hosting firewall rejects such code sent as plain text with a bare 403 Forbidden. When in doubt, always use base64. FORMS: a page can collect replies (RSVP, order, contact, sign-up) with a plain ; each field needs a name attribute, replies go to the owner's dashboard and email, visitors never log in. Add against spam, and optionally to send the visitor to your own thank-you page. No file uploads in forms. A brand-new address usually gets HTTPS within a few minutes, rarely up to 15 (the browser shows a secure-connection error until then); always pass that on to the user when the result says ready: false.

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

Input Schema

NameRequiredDescriptionDefault
htmlNoFull HTML of the home page (index.html), plain text. Only for pages WITHOUT <script> or on*= attributes; pages with JavaScript must go through files with encoding "base64" or the request is refused with 403 by the hosting firewall.
nameYesThe site name: letters, numbers, hyphens. Becomes <name>.nsd.sg. Use an existing site name to update it.
filesNoFiles to publish, e.g. [{path:"index.html", content:"..."}, {path:"style.css", content:"..."}]. Any file containing <script>, on*= attributes or javascript: MUST be sent as {path, content: <base64 of the UTF-8 text>, encoding: "base64"}; images, fonts and PDFs likewise as base64. Max 100 files, 8 MB total; a build output bigger than that goes up as a ZIP from the dashboard. Special files: 404.html = the site's own not-found page; _redirects (one rule per line: "/old /new 301", "/* /index.html 200" for a single-page app) = same-site redirects only.
titleNoOptional label shown only in the owner's dashboard.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

With no annotations, the description carries the whole burden and does so: it warns that script/on*/javascript: content sent as plain text is rejected with a bare 403 by the hosting firewall, that existing files are preserved on update, that forms post to nsd.sg/f/<name> with no visitor login and no file uploads, and that new sites may lack HTTPS for up to 15 minutes. These are exactly the failure modes an agent would otherwise hit blindly.

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?

Purpose is front-loaded in the first sentence, and the caps-labeled IMPORTANT/FORMS blocks are scannable. The forms section is long and somewhat tangential to the core publish action, and a few points (base64 rule) are restated three times, but nearly every sentence carries operationally useful content.

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?

For a mutation tool with no annotations and no output schema, the definition covers the return value ('Returns the live URL'), the ready:false HTTPS provisioning caveat and the instruction to relay it to the user, plus size limits and redirect/404 special files. An agent has everything needed to call it correctly and interpret the result.

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 already 100%, so the baseline is 3; the description still adds decision value beyond it, notably the 'when in doubt, always use base64' heuristic and the framing of html as the home page only. It largely restates schema detail (limits, special files, encoding), which caps it below 5.

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 and resource ('Put a page online at <name>.nsd.sg') and clarifies both modes: creating a new site and adding/replacing files on an owned site. The dual input path (full HTML vs. file list) is spelled out, so an agent knows exactly what the tool does without opening the 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?

Gives clear situational guidance: use html for simple pages, files for anything with scripts or binaries, and 'when in doubt, always use base64.' It also notes the site-is-created-if-absent behavior. It does not explicitly point to siblings like nsd_update or nsd_read_file or say when not to use this tool, so it stops short of full routing guidance.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.