Skip to main content
Glama

Set guest access to lists

set_folder_guest_access
DestructiveIdempotent

Give guests access to lists of the current user (the Lists of My games), or take it away. Guests are the people the user invites to play with an access code; access goes to one guest, to a group of guests or to all of them. Get the ids of guests and groups from list_my_guests and list_my_guest_groups. Lists of other users come back in "failed" as "forbidden", and only the first 50 list ids are used. Same as POST users/{idUser}/folders/ with action=setGuestAccess 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": "set_folder_guest_access"
  }
}

Input Schema

NameRequiredDescriptionDefault
addNoWho gets access to those lists.
idsYesIds of the lists, from list_my_folders.
removeNoWho loses access to those lists.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true and idempotentHint=true, so the description correctly reinforces the revoke path rather than the safety profile. It adds real behavior beyond annotations: the three granularities of grantee, the per-user failure mode ("forbidden" in "failed"), the 50-list cap, and that the API's JSON/error body is returned in "response". It doesn't say what happens when add and remove target the same list or guest.

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?

Front-loaded with the action and then layered with sourcing, failure, limit, and API mapping — every sentence carries information. Some phrasing is convoluted ("the Lists of My games") and it reads as one dense block rather than distinct statements.

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 usefully explains that the REST body or error body comes back in "response", and it covers the main failure case. Minor gaps remain (add/remove optionality and overlap, what an empty add or remove means) for a mutation tool.

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?

Schema coverage is 100%, so the baseline is 3; the description still adds meaning by tying ids to list_my_folders and by disclosing the 50-id truncation limit, which the schema does not state. It does not explain the interaction between add and remove.

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?

States a specific verb+resource — granting or revoking guest access to the current user's lists — and clarifies the resource scope ("Lists of My games") plus who a guest is. This is clearly distinguishable from the read-side sibling get_folder_guest_access.

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?

Tells the agent where the ids come from (list_my_guests, list_my_guest_groups, list_my_folders) and warns that other users' lists cannot be targeted. It does not explicitly contrast with get_folder_guest_access or say when to prefer this over per-guest updates, but the conditions for correct use are otherwise clear.

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