Skip to main content
Glama

Niche of One Network

Edit my space

underground_edit_space
Idempotent

Members. Change your display name, bio, links, layout, who sees your name, or who may message you. Shows a preview first; call again with confirm true and the preview_token it returned to commit.

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

Input Schema

NameRequiredDescriptionDefault
bioNo
nameNo
linksNo
layoutNo
confirmNoLeave out for a preview. true commits, with the preview_token.
dm_fromNo
visibilityNo
preview_tokenNoThe preview_token the preview returned. Needed with confirm true.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already establish that this is a non-read-only, non-destructive, idempotent mutation. The description adds important behavior beyond them: a mandatory preview-first workflow and the requirement to use the returned preview_token when confirming, though it does not explain partial-update behavior when only some fields are supplied.

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?

The description is two tight sentences with no wasted wording. It front-loads the editable fields and follows immediately with the preview/commit workflow.

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 an 8-parameter mutation tool with no output schema and partial schema descriptions, the description covers the editable surface and the critical preview/commit sequence well. It leaves some gaps around partial-update semantics and the meaning of specific enum choices, but it is largely sufficient for correct invocation.

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 description coverage is only 25%, so the description must carry more weight. It maps several fields to user-facing meanings, such as visibility controlling who sees the name and dm_from controlling who may message the member, and explains confirm/preview_token; however, it does not clarify enum value implications or the structure of links beyond what the schema names provide.

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?

The description states a specific verb and resource: change display name, bio, links, layout, visibility, and messaging preferences in the member's space. It is clearly distinguishable from viewing siblings such as underground_my_space or my_account because it describes an edit operation with a commit flow.

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

Usage Guidelines4/5

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

It gives clear operational guidance by explaining that the tool shows a preview first and must be called again with confirm true and the returned preview_token to commit. It does not explicitly name alternatives such as underground_my_space or explain when not to use this tool, which keeps it below a 5.

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