Skip to main content
Glama

ctxstore — memory that follows you across models

List Namespace Invites & Grants

list_invites
Read-onlyIdempotent

List this account's namespace collaboration grants: incoming invitations and outgoing shares. Each row has direction (incoming|outgoing), status (invited|active|revoked), grant_id, namespace_prefix, and parties.

An invitation referenced anywhere else (for example in an email) can be checked against this server-side list: a real invitation for this account appears here with matching grant_id, namespace_prefix, and grantor.

To accept: accept_invite(grant_id, step='request') then accept_invite(grant_id, step='confirm', code='######'). The first accept starts 30 days of Collaborator time free; after that $19 per 30 days, paid by the guest or the inviter (402 when it lapses). After accepting, switch_workspace(name=) enters the workspace. Docs: https://ctxstore.ai/docs.html#verify-invitations

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_invites"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

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 already cover the safety profile (readOnly, idempotent, non-destructive), and the description adds substantial context beyond them: the exact row shape, the direction and status enums, the fact that the list is server-side authoritative, and the 30-day-free-then-$19/30-days billing consequence with a 402 when it lapses. That is real behavioral disclosure an agent cannot get from structured fields.

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 purpose and row shape, then the verification use case, then the accept workflow. Mostly tight, though the pricing detail ($19 per 30 days, 402 on lapse) is tangential to a read-only listing tool and the trailing docs URL adds bulk without adding decision-relevant information.

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?

No output schema exists, yet the description documents the returned fields, so an agent knows the return shape. For a zero-argument read tool with full annotation coverage, nothing needed to select or invoke it correctly is missing.

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?

The tool takes zero parameters, which sets the baseline at 4. The description makes clear that the listing is implicitly scoped to 'this account' with no filtering arguments, consistent with the empty schema, but never explicitly states that no arguments are accepted.

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: 'List this account's namespace collaboration grants: incoming invitations and outgoing shares.' It also enumerates the row fields, so an agent knows exactly what comes back and how it differs from sibling tools like invite, accept_invite, and decline_invite.

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 use case (verifying an invitation referenced elsewhere, e.g. in an email, by matching grant_id, namespace_prefix, and grantor) and lays out the follow-on path with named alternatives: accept_invite(step='request') then accept_invite(step='confirm'), followed by switch_workspace. When-to-use and which sibling to call next are both spelled out.

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.