Skip to main content
Glama

ctxstore — memory that follows you across models

Invite Someone to a Namespace

invite
Idempotent

Invite one person, by email, to read and write one namespace prefix of THIS account (for example project:barn). Creates a pending grant and emails them; nothing is shared until they accept with list_invites and accept_invite from their own account. Calling again for the same person and prefix returns the existing invitation without a second email. Withdraw with revoke_grant(grant_id). Not available from a shared workspace session. Their first 30 days of Collaborator time are free; after that you can pay their $19 per 30 days from /account. You are emailed when they accept, and list_workspaces shows whether they have entered yet. 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": {
      "email": "<email>",
      "namespace_prefix": "<namespace_prefix>"
    },
    "name": "invite"
  }
}

Input Schema

NameRequiredDescriptionDefault
noteNoOptional short note shown verbatim in the email (max 1000 chars).
emailYesThe invitee's email address.
write_prefixesNoOptional: narrow WRITES to these prefixes (each further scoped to '<prefix>:<agent_id>' after bind_agent). Omit to write where they read.
exclude_prefixesNoOptional deny list under the shared prefix: facts whose key or namespace sits under one of these are invisible to the invitee.
namespace_prefixYesKey prefix to share, e.g. 'project:barn'. No wildcards.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / exclude_prefixes
      Added value: +{
      +  "description": "Optional deny list under the shared prefix: facts whose key or namespace sits under one of these are invisible to the invitee.",
      +  "items": {
      +    "type": "string"
      +  },
      +  "type": "array"
      +}
    • addedInput schema / properties / write_prefixes
      Added value: +{
      +  "description": "Optional: narrow WRITES to these prefixes (each further scoped to '<prefix>:<agent_id>' after bind_agent). Omit to write where they read.",
      +  "items": {
      +    "type": "string"
      +  },
      +  "type": "array"
      +}
  2. Added

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare non-read-only, open-world, idempotent, non-destructive behavior, but the description adds substantive context beyond them: a pending grant is created, an email is sent, repeat calls for the same person/prefix return the existing invitation without a second email, the caller is emailed on acceptance, and list_workspaces reveals whether the invitee has entered. It omits details like exact error modes or rate limits, which keeps it just short of a 5.

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?

Front-loaded with the core action and scope, then flow, idempotency, withdrawal, and availability constraints in logical order. Dense but nearly every sentence carries operational value; the pricing and 30-day-free details are tangential to invocation but arguably useful for the agent to relay to a user.

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 5-parameter mutation tool with no output schema, the definition covers who is invited, what is shared, what happens until acceptance, how to revoke, how to verify status, and the session-type restriction. An agent has everything needed to call it correctly and to explain the outcome.

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 description coverage is 100%, so email, namespace_prefix, note, write_prefixes, and exclude_prefixes are already documented in the schema. The description only reinforces the read-and-write default scope of the shared prefix and the 'one person, one prefix' constraint, adding modest meaning over structured data; baseline 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 with precise scope: invite one person by email to read and write one namespace prefix of THIS account, with a concrete example (project:barn). It distinguishes itself from siblings by naming accept_invite, list_invites, revoke_grant, and list_workspaces, so an agent can route correctly without opening other schemas.

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?

Explicitly explains the workflow: the invite creates a pending grant, nothing is shared until the recipient accepts via list_invites/accept_invite from their own account, and withdrawal happens through revoke_grant(grant_id). It also names a hard exclusion (not available from a shared workspace session) and states repeat-call behavior, leaving little to inference.

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.