Skip to main content
Glama

ctxstore — memory that follows you across models

Accept Namespace Invitation

accept_invite

Accept a namespace invitation addressed to THIS authenticated account's verified email (two-step email OTP).

Steps:

  1. step='request' — emails a 6-digit code to the invited address (may return 402 needs Collaborator, or 503 if mailer fails).

  2. step='confirm' with code= the 6 digits — activates the grant. Then switch_workspace(name=) enters it on this same connection (mcp_config with the X-Ctxstore-Workspace header is also returned for header-based clients).

The code activates the named grant_id only; it authorizes nothing else. Obtain grant_id from list_invites(). Docs: https://ctxstore.ai/docs.html#verify-invitations

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>",
      "step": "<step>"
    },
    "name": "accept_invite"
  }
}

Input Schema

NameRequiredDescriptionDefault
codeNo6-digit code from email (required when step=confirm).
stepYesrequest = send OTP email; confirm = submit code.
grant_idYesUUID of the invitation (from list_invites or invite email).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations only flag it as non-read-only, open-world, non-idempotent, non-destructive; the description adds far more — a code is emailed, 402 means the caller needs Collaborator, 503 means the mailer failed, and the code activates only the named grant_id and nothing else. That failure-mode and blast-radius detail is exactly what annotations cannot convey.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The opening sentence states purpose and the numbered steps make the two-phase flow scannable with no filler. The parenthetical error codes and header note are dense but each carries operational value; the trailing docs URL is the only arguably dispensable element.

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 three-parameter, two-phase mutation with no output schema, the description covers prerequisites (list_invites), both error branches, the scope of the authorization granted, and the post-success handoff. An agent has everything needed to invoke it correctly on the first attempt.

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 baseline is 3; the description earns above that by explaining what each step value actually does (sends the email vs. submits the code), that code is required only for confirm, and where grant_id originates. It stops short of describing the code's format/lifetime beyond '6-digit', which the schema already covers.

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 ('Accept a namespace invitation') and immediately narrows scope to invitations addressed to THIS authenticated account's verified email via two-step OTP. It also distinguishes itself from list_invites (the source of grant_id) and points to switch_workspace as the follow-up, so an agent can place it in the invitation workflow without opening another 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?

Gives an explicit ordered protocol: step='request' first, then step='confirm' with the 6-digit code, plus the prerequisite that grant_id comes from list_invites(). It also names the successor action (switch_workspace(name=<grantor>) or the X-Ctxstore-Workspace header path) so the agent knows what to do after success.

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.