Skip to main content
Glama

List my guest groups

list_my_guest_groups
Read-onlyIdempotent

List the groups of guests of the current user, with how many guests each one has and the games and lists the group can open. Use the ids with set_folder_guest_access. Same as GET users/{idUser}/guests/groups/ of the Educaplay REST API, for the current user: its JSON body, or its error body, comes in "response".

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, closed-world and non-destructive, so the safety profile is covered. The description adds genuinely useful behavior beyond that: the payload includes per-group guest counts and the games/lists each group can open, and both the success JSON and error body are wrapped in a 'response' field. That wrapping detail is the most valuable disclosure since there is no output schema, but the description gives no pagination, sorting, or empty-result behavior.

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?

It is compact and front-loads the purpose before the downstream usage hint and the API equivalence note. The final clause about the 'response' envelope is slightly run-on and would read better as its own sentence.

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?

With no output schema, the description must carry the return-value burden, and it names the main fields plus the response envelope for both success and error. For a zero-argument read tool this is close to complete, though pagination and the shape of the nested game/list entries are unstated.

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 there is nothing for the description to disambiguate; the baseline of 4 applies. The description correctly implies the scope is implicit (the current user) rather than parameterized.

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 states a specific verb and resource ('List the groups of guests of the current user') and enumerates the returned contents (guest counts, openable games and lists), which distinguishes it from the sibling list_my_guests that returns guests rather than groups. An agent can tell what this returns without opening anything else.

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 gives concrete downstream guidance — 'Use the ids with set_folder_guest_access' — which effectively says when the result matters and names the sibling that consumes it. It does not explicitly exclude alternatives such as list_my_guests or get_folder_guest_access, so it stops short of full when/when-not routing.

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