Skip to main content
Glama

ctxstore — memory that follows you across models

Leave Active Namespace Grant

leave_grant
DestructiveIdempotent

Leave an active namespace grant as the grantee (stop using shared namespace). Server verifies grantee authorization. Grantors who want to cut off a collaborator must use revoke_grant.

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": {
      "grant_id": "<grant_id>"
    },
    "name": "leave_grant"
  }
}

Input Schema

NameRequiredDescriptionDefault
grant_idYesUUID of the active grant to leave.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Goes beyond the annotations by disclosing the authorization check ('Server verifies grantee authorization') and the actor prerequisite (must be the grantee), neither of which is expressible in the provided hints. The annotations already cover destructiveness and idempotency, so the description only needs to add this kind of context, which it does; what is not stated is what happens to the collaborator's data or history after leaving.

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?

Three short sentences, front-loaded with the action and effect, followed by the auth note and the alternative routing. No filler or restated title text.

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 mutation with full annotation coverage, the definition covers the actor role, the authorization behavior, and the sibling alternative. The remaining gap is what a departing grantee loses or retains (data, history, re-entry ability), which an agent might reasonably want before invoking a destructive tool.

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?

With one parameter at 100% schema description coverage, the schema already defines grant_id as the UUID of the active grant. The description adds no format, sourcing, or constraint detail beyond that, so the baseline of 3 applies.

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 ('Leave an active namespace grant') plus the actor role ('as the grantee') and the practical effect ('stop using shared namespace'). It is immediately distinguishable from revoke_grant, which the description explicitly attributes to grantors.

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 when-to-use (you are the grantee leaving) and an explicit when-not/alternative (grantors cutting off a collaborator must use revoke_grant). The role split removes any ambiguity between the two sibling tools.

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.