Skip to main content
Glama

Get webspace details

webspace_get
Read-only

Get full detail for a webspace including linked domains and live disk usage in GB (probed via SSH).

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

Input Schema

NameRequiredDescriptionDefault
idYesThe webspace ID

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description still adds real behavioral context: the disk usage figure is 'live' and 'probed via SSH', warning the agent that the call reaches out to the host and may be slow or fail if SSH is unreachable.

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?

One sentence, front-loaded with the resource and verb, then the returned fields, with the SSH caveat parenthetical in the right place. No wasted words.

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 single-parameter read tool with no output schema, the description covers what comes back (domains, disk usage in GB) and how it is obtained. Only the failure/slow-path behavior when the SSH probe fails is left unstated.

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 the single 'id' parameter is fully documented in the schema, so baseline is 3. The description adds no extra constraint or format meaning for the ID beyond what the pattern already encodes.

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 description gives a specific verb ('Get') and resource ('a webspace') and enumerates the payload: linked domains and live disk usage in GB. It does not name a sibling to distinguish itself from, but 'webspace' plus 'full detail' is clear enough to separate it from the vps_get family.

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?

Nothing states when to call this rather than webspace_list, webspace_get_ssh_info, or vps_get, nor any prerequisite such as needing a known 24-hex ID. Usage is only implied by 'Get full detail'.

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.