Skip to main content
Glama

get_my_pending_org_invitations

Read-only

Organization invitations this coach has received and not yet responded to (e.g. an invite to join a gym as staff).

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/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 and scope are covered structurally. The description adds that results are limited to the calling coach and to pending status only, which is useful, but it says nothing about result volume, ordering, or whether expired invites are included.

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?

One sentence, front-loaded with the resource and scope, with the parenthetical example earning its place by disambiguating 'organization invitation.' No wasted wording, though it could be tightened slightly.

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 zero-parameter, non-destructive read with no output schema, the description supplies everything needed to select and invoke it: what is returned, whose data, and which status filter applies. Remaining gaps (pagination, ordering) are minor for this complexity level.

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, so the baseline is 4. The description correctly signals that no filtering input is needed because the pending/received scope is implicit in the call itself.

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 resource with clear scope: organization invitations 'this coach has received and not yet responded to,' plus a concrete example (gym staff invite). This is well beyond a restatement of the name, but it never explicitly contrasts itself with siblings like list_invitations, leaving the received-vs-sent distinction to inference.

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?

'not yet responded to' implies the use case (checking invites awaiting an action) without stating it. There is no explicit when-to-use statement, no exclusion, and no pointer to an alternative tool for already-responded or sent invitations.

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.