Skip to main content
Glama

nsd_read_file

Read one file of a live site, exactly as it is online now. Use it before a small change ("change the price", "fix the date") in a chat that does not have the page yet: read the file, change only what the user asked, then send it back with nsd_publish under the same name. Text files come back as text, images and other binary files as base64. Max 1 MB.

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>",
      "path": "<path>"
    },
    "name": "nsd_read_file"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYesThe file path as nsd_get_site lists it, e.g. index.html.
site_idYesThe site id from nsd_list_sites.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

No annotations exist, so the description carries the burden, and it does disclose the two facts an agent most needs: text files return as text while binary returns as base64, and there is a 1 MB ceiling. It omits failure behavior (missing path, oversized file) and any permission requirements, leaving some gaps.

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?

Three tight sentences plus a size note, front-loaded with the action and followed by the workflow and return-format caveats. Every sentence carries distinct information; nothing is padded.

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 two-parameter read tool with no output schema, the description covers return encoding, size limit, and next step — enough to call it correctly. Missing only error/failure semantics and permission assumptions, which are secondary for a read operation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/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 in-schema, including the cross-reference to nsd_get_site for path format. The description adds nothing about parameter semantics beyond what the schema already says, so the baseline of 3 applies.

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 — 'Read one file of a live site' — and pins down scope with 'exactly as it is online now', distinguishing a single-file read from the site-level siblings (nsd_get_site, nsd_list_sites). An agent knows immediately what this returns.

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?

Gives an explicit triggering condition ('before a small change ... in a chat that does not have the page yet'), which doubles as a when-not rule: skip it if the page is already in context. It also names the follow-up tool (nsd_publish under the same name), so the whole workflow is routed.

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.