Skip to main content
Glama

Create list

create_folder

Create a list for the current user (the Lists of My games). Lists cannot go inside other lists. On plans below Academic an account can have at most 3 lists, and creating one more fails with "folder_limit_reached". Same as POST users/{idUser}/folders/ with action=create of the Educaplay REST API, for the current user: its JSON body, or its error body, comes in "response". The new list comes in "folder".

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": {
      "name": "<name>"
    },
    "name": "create_folder"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesName of the list, at most 50 characters and different from the names of the other lists of the user.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false and destructiveHint=false, so the safety profile is covered. The description adds real behavioral context beyond that: the quota limit, the failure code, and the equivalences to the Educaplay REST endpoint. The response-shape sentence ('response', 'folder') is useful but borders on restating what an output schema would carry. A 3 reflects solid but not especially rich added context given annotations already exist.

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-loads the purpose and immediate constraints, then trails into API-mapping detail. Every sentence is informative, though the closing sentence about the REST endpoint and JSON body is dense and slightly redundant given the response-key note.

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 single-parameter creation tool with no output schema, the description supplies quota limits, error behavior, non-nesting rules, and the names of the returned fields ('response' and 'folder'). An agent has everything needed to call it and interpret the result.

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?

Schema description coverage is 100%, and the single 'name' parameter is already documented in the schema with both the 50-character limit and the uniqueness requirement. The description adds no syntax or format guidance beyond that, so the schema carries the parameter burden and baseline 3 applies.

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 and resource ('Create a list') plus the owning scope ('for the current user', 'Lists of My games'), and adds the non-obvious constraint that lists cannot nest inside other lists. That clearly separates it from siblings like create_activity or list_my_folders.

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?

Gives concrete when-not conditions: no nesting inside other lists, and a hard cap of 3 lists on plans below Academic with the exact failure code 'folder_limit_reached'. It does not name a sibling alternative for managing existing lists, but the usage constraints are explicit enough to guide invocation.

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