Skip to main content
Glama

list_invitations

Read-only

List invitations the coach has sent to prospective clients (pending, accepted, rejected).

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_invitations"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageSizeNo
pageNumberNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds only the status set as a hint about returned records; it says nothing about ordering, whether results are scoped to the authenticated coach, or how pagination behaves. That is modest added value over the structured annotations.

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?

A single well-formed sentence with the scope and statuses front-loaded and no filler. It is appropriately tight, though the brevity leaves the pagination gap to other dimensions.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple read-only list this covers purpose and result statuses, but with no output schema and undocumented pagination parameters, an agent lacks enough to predict page size limits or result shape. Adequate but with clear gaps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Both parameters (pageSize, pageNumber) have 0% schema description coverage, and the description never mentions pagination, defaults, or maximums. An agent calling this must consult raw schema constraints alone, so the description fails to compensate for the coverage gap.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ("List invitations") plus the scope "the coach has sent to prospective clients," and enumerates the statuses covered. It does not name or distinguish any sibling such as get_my_pending_org_invitations, so an agent must still infer which list tool covers org-level pending invitations.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The parenthetical "(pending, accepted, rejected)" implicitly tells the agent this returns all statuses rather than only pending, which is a mild usage constraint. There is no explicit when-to-use, when-not-to-use, or alternative-tool routing guidance, so the agent has to infer the boundaries.

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.