Skip to main content
Glama

nsd_get_site

One site: URL, status, files, storage used and the plan's limits.

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_get_site"
  }
}

Input Schema

NameRequiredDescriptionDefault
site_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3/5.0
Behavior3/5

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

With no annotations, the description must carry the behavioral load. It does disclose what is returned (URL, status, files, storage used, plan limits), which partly substitutes for the absent output schema, but says nothing about read-only semantics, permission requirements, or what happens with an unknown site_id.

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?

A single short fragment with no filler, and the key fact (single site) is front-loaded. The phrasing is a noun list rather than a sentence, which is terse but still readable.

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

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a one-parameter read tool the description is close to adequate, and the return-field enumeration compensates for the missing output schema. The gap is the parameter itself and error behavior, which remain entirely unspecified.

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

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% and the sole parameter site_id is undocumented in the schema. The description adds no meaning about its format, where to obtain it, or whether it is an ID versus a domain, so the agent gets no help beyond the property name.

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?

The phrase 'One site' plus the enumerated payload (URL, status, files, storage used, plan limits) makes clear this retrieves a single site's details, implicitly distinguishing it from the sibling nsd_list_sites. It lacks an explicit verb, but the resource and scope are unambiguous.

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

Usage Guidelines2/5

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

No when-to-use guidance is given: nothing says to call this when you already have a site_id versus calling nsd_list_sites first to discover one. The 'One site' contrast is the only hint, and alternatives are never named.

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.