Skip to main content
Glama

ctxstore — memory that follows you across models

Decline Namespace Invitation

decline_invite
DestructiveIdempotent

Decline a pending (status=invited) namespace invitation as the grantee. Server verifies you are the invitee (email/tenant match). Grantors must use revoke_grant instead.

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": "decline_invite"
  }
}

Input Schema

NameRequiredDescriptionDefault
grant_idYesUUID of the invitation to decline.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, idempotentHint=true, and readOnlyHint=false. The description adds useful behavioral context beyond those annotations by stating the server verifies invitee identity via email/tenant match and that only status=invited invitations are eligible. It does not describe the post-decline state or side effects, which is a minor gap for a destructive action.

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 core action and followed by preconditions and the sibling alternative. Every sentence carries useful information with no unnecessary wording.

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 one-parameter mutation with rich annotations and no output schema, the definition covers eligibility, identity verification, and alternative routing. It stops short of describing the resulting state after a successful decline, but that is not required to invoke the tool correctly.

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?

Schema coverage is 100%, so the grant_id format is already documented. The description adds meaningful semantic constraint by indicating the grant_id must refer to a pending invitation with status=invited and must belong to the authenticated grantee.

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: decline a pending namespace invitation. It also scopes the action to the grantee and distinguishes it from revoke_grant, so an agent can identify the 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 explicitly says to use this as the grantee for a pending invitation and directs grantors to revoke_grant instead. The main alternative for an invitee, accepting the invitation, is implicitly clear from the verb decline.

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.