Skip to main content
Glama

ctxstore — memory that follows you across models

Revoke Namespace Grant (Grantor)

revoke_grant
DestructiveIdempotent

Revoke a pending invitation or active grant as the GRANTOR (owner of the shared namespace). Idempotent. Grantees use decline_invite / leave_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": "revoke_grant"
  }
}

Input Schema

NameRequiredDescriptionDefault
grant_idYesUUID of the grant to revoke.

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?

Annotations already declare destructive and idempotent behavior, while the description adds useful context: it can revoke pending invitations or active grants and requires grantor ownership. It repeats idempotency from annotations and does not spell out the immediate effect on active access, but the authorization and scope context are clear.

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 definition is three short sentences with no wasted wording. The core action and actor role are front-loaded, and the final sentence efficiently routes grantees to the correct alternative tools.

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 simple one-parameter destructive tool, the description covers the action, actor role, idempotency, and alternatives, while annotations handle the safety profile and the schema documents the parameter. It could more explicitly state the effect on active access, but it is complete enough to call correctly.

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?

The schema has 100% description coverage for the single grant_id parameter and already explains that it is the UUID of the grant. The description adds no additional parameter-level meaning, so the baseline score 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?

The description gives a specific verb and resource: revoke a pending invitation or active grant. It explicitly distinguishes the actor role (GRANTOR, owner of the shared namespace) and names sibling tools used by grantees, so an agent can identify this tool without opening the schema.

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?

It states when this tool applies: as the grantor, to revoke either a pending invitation or an active grant. It also names the alternatives for grantees, decline_invite and leave_grant, making the role-based routing explicit.

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.