Skip to main content
Glama

Read your invite link

invites
Read-onlyIdempotent

Your invite link code and the players who joined through it, with the rewards they earned you, exactly like the web client's invite window (GET /v1/invites). Someone new joins through you by passing your code as invite to register or guest_login.

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

Input Schema

NameRequiredDescriptionDefault
tokenNothe token your login returned; pass it when a call answered not_logged_in after you logged in

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties
      Added value: +{
      +  "token": {
      +    "description": "the token your login returned; pass it when a call answered not_logged_in after you logged in",
      +    "type": "string"
      +  }
      +}
  2. First observed

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint false and openWorldHint false, so safety and idempotency are covered. The description adds useful context that the payload mirrors the web client's invite window and names the backing endpoint, but says nothing about empty-state behavior or reward aggregation semantics. With annotations carrying the behavioral profile, a 3 is appropriate.

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

Conciseness5/5

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

A single dense sentence front-loads the resource and its contents, then adds the join mechanic and endpoint mapping. Nothing is redundant and no sentence is wasted.

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

Completeness4/5

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

An output schema exists, so return values need not be described, and the description is complete enough to call the tool correctly. The only minor gap is that it does not hint at how to recover from not_logged_in beyond what the schema's token description already covers.

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?

There is only one optional token parameter and schema description coverage is 100%, with the schema itself explaining the re-auth retry case. The description adds nothing about the token, but the baseline of 3 applies since the schema fully documents it.

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?

The description names the exact resource and scope: the caller's invite link code, the players who joined through it, and the rewards earned. It even maps to the web client's invite window and the underlying endpoint GET /v1/invites, which clearly distinguishes it from siblings like find_players or account.

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

Usage Guidelines4/5

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

It explains the mechanic of use - someone joins through you by passing your code as invite to register or guest_login - which tells the agent what this data is for and how it is produced. It does not explicitly say when to prefer this over sibling tools, but the resource is narrow enough that no ambiguity remains.

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.

Resources