Skip to main content
Glama

nsd_update

Replace ALL files of an existing site with the given HTML or files. Older versions are kept and can be restored from the dashboard. Same rule as nsd_publish: anything containing , on*= attributes or javascript: must be sent as files with encoding "base64", or the hosting firewall refuses it with 403.

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

Input Schema

NameRequiredDescriptionDefault
htmlNoFull HTML of the new home page, plain text, only when it has no <script> or on*= attributes; otherwise use files with encoding "base64".
filesNo
site_idYesThe site id from nsd_list_sites.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

No annotations are supplied, so the description carries the full load, and it does disclose two non-obvious traits: previous versions are retained and restorable from the dashboard, and non-compliant content is rejected by the firewall with a 403. It still omits permissions/auth requirements and the response shape, and does not spell out that files present on the site but omitted from the request are removed.

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?

Three sentences, front-loaded with the destructive 'replace ALL' scope, then the recovery guarantee, then the encoding constraint. Dense and mostly waste-free, though the encoding rule is restated in the html parameter description, producing mild redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/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 risky parts well: full-overwrite semantics, version retention, and the base64 firewall constraint. Remaining gaps are authorization/prerequisite context and explicit confirmation of what an omitted file path means.

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 67%, and the description adds meaning beyond the schema by explaining why the base64 encoding path exists (firewall 403), plus the tool-level constraint that script/on*/javascript: content forces the files route. It doesn't clarify what happens to files not listed in the array or whether site_id accepts anything other than an id from nsd_list_sites.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and scope: 'Replace ALL files of an existing site'. The 'existing site' wording is what implicitly separates it from the publish sibling, but the description never states that contrast directly.

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

Usage Guidelines3/5

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

It gives a clear rule for choosing html vs files (script-free content as plain html, otherwise base64 files), which is real usage guidance. It never says when to call nsd_update instead of nsd_publish, only that they share the same firewall rule, so the update-vs-create decision 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.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.