Skip to main content
Glama

Get guest access to lists

get_folder_guest_access
Read-onlyIdempotent

Tell who can open each of the given lists of the current user (the Lists of My games): "all" true means every guest of the user, "groupIds" and "guestIds" are the groups and the guests with access, and "guests" gives the names of those guests. Same as GET users/{idUser}/folderguests/?ids= of the Educaplay REST API, for the current user: its JSON body, or its error body, comes in "response".

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "ids": "<ids>"
    },
    "name": "get_folder_guest_access"
  }
}

Input Schema

NameRequiredDescriptionDefault
idsYesIds of the lists, from list_my_folders.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds useful context beyond that: it explains the return structure (all, groupIds, guestIds, guests) and states that the JSON body or error body is delivered in a 'response' field, which is valuable behavioral detail absent from annotations.

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

Conciseness3/5

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

The core purpose is stated first, which is good, but the single long sentence is cluttered with quoted field names and an embedded REST path. It is serviceable but not tightly structured, and the API-reference clause could be trimmed or separated.

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 only one required parameter, no output schema, and annotations covering safety, the description does the important remaining work by explaining the response fields and error handling. It is nearly complete for a tool of this complexity, missing only explicit guidance on alternatives.

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 a single parameter with 100% schema description coverage, so the schema already documents the ids array and its source (list_my_folders). The description restates the resource scope but adds no format, limits, or ordering semantics for the ids beyond what the schema provides, making the baseline 3 appropriate.

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?

The description gives a specific verb and resource: it tells who can open each of the given lists belonging to the current user. It clarifies the read-only nature and the meaning of each returned field. It does not explicitly distinguish itself from set_folder_guest_access, though the wording 'Tell who can open' clearly implies retrieval rather than mutation.

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?

Usage is implied by 'the given lists of the current user' and the schema note that ids come from list_my_folders, giving an agent a starting point. There is no explicit when-to-use guidance, no statement of when not to use it, and no naming of set_folder_guest_access as the mutating alternative.

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