Skip to main content
Glama

Remove a Niche from Spaces

remove_niche_spaces
Destructive

Remove a niche from one or more Spaces to revoke access for their members. Handles multiple Space IDs in a single all-or-nothing call.

Instructions

Use this to take a niche out of one or more Spaces (ids from list_spaces). A Space controls who can see the niche, so adding or removing one changes access. Returns removed and notPresent. Undo with add_niche_spaces. The same rights as the web app: the user needs Manage access to the niche, and to every Space added or removed. A refusal is a 403, so tell the user instead of retrying. A change is all or nothing: if any id is unknown, or a Space is one the user has only view rights on, the whole call fails and nothing changes (the error lists the offending ids). Ids already in the wanted state are counted, never errors, so a repeat is safe. Costs nothing. Limited to 2 calls per minute per niche, so put every id in one call.

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": {
      "nicheId": "<nicheId>",
      "spaceIds": "<spaceIds>"
    },
    "name": "remove_niche_spaces"
  }
}

Input Schema

NameRequiredDescriptionDefault
nicheIdYesThe niche to change. Get one from `list_niches`.
spaceIdsYesThe ids of the Spaces to take the niche out of, 1-100, unique. Get them from `list_spaces`.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.20.1

TDQS

A4.7/5.0
Behavior5/5

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

Goes well beyond the destructiveHint/readOnlyHint annotations: permission requirements (Manage on the niche and every Space), a 403 refusal that must not be retried, all-or-nothing atomicity with offending ids in the error, idempotent repeats ('ids already in the wanted state are counted, never errors'), zero cost, and a 2-calls-per-minute-per-niche limit.

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?

Front-loads the action, then stacks the operational facts (permissions, failure modes, idempotency, cost, rate limit) in short declarative sentences. There is no filler and no repetition of the tool name.

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

Completeness5/5

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

For a destructive bulk mutation with no output schema, it names the returned fields (`removed`, `notPresent`), covers auth, partial-failure semantics, retry safety, and throttling. Nothing an agent needs before calling is missing.

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 already documented with their sources (list_niches, list_spaces). The description's only added parameter-level meaning is the batching directive, which constrains how spaceIds should be populated but does not describe formats or units beyond the schema.

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 ('take a niche out of one or more Spaces') and immediately clarifies the meaning of a Space. It is trivially distinguishable from the sibling add_niche_spaces and from remove_niche_labels/remove_niche_keywords.

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 undo path ('Undo with add_niche_spaces') and an explicit batching instruction ('put every id in one call') tied to the rate limit, so the agent knows both the alternative and how to avoid throttling.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.