Skip to main content
Glama

Niche of One Network

My Underground space

underground_my_space
Read-onlyIdempotent

Members. Your own profile, space settings and the rooms you can post in.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "underground_my_space"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so the safety profile is fully covered by structured data. The description does contribute that the payload spans three distinct domains (profile, space settings, postable rooms), but says nothing about scoping to the authenticated member or what happens for a user with no space.

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?

It is a single short sentence with no filler, which is appropriate for a no-argument tool. The structure is weakened by the detached "Members." fragment, which reads as an audience tag rather than leading information.

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?

With no input parameters and no output schema, the description carries the burden of explaining what comes back, and it does so only at a high level — three named domains but no sense of shape, size, or nesting. It is adequate to identify the tool's subject but thin for an agent that must decide whether a single call covers profile and room-permission needs.

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?

The tool takes zero parameters, so there is no parameter meaning for the description to supply; the baseline for a parameterless tool applies. The description's mention of the three returned domains is a light substitute for the absent parameter list rather than genuine parameter semantics.

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

Purpose3/5

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

The description names the resources involved ("your own profile, space settings and the rooms you can post in") but has no verb at all, so the agent must infer this is a read of the caller's own space rather than a list or a mutation. It is distinguishable from underground_edit_space only by implication, and the leading fragment "Members." adds ambiguity rather than a stated purpose.

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?

There is no when-to-use guidance and no named alternative — nothing tells the agent to prefer this over my_account, my_brief, or underground_edit_space when the caller wants profile versus space configuration. The reader must rely entirely on the tool name and sibling naming to route correctly.

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.

Resources