Skip to main content
Glama

Rename list

rename_folder
DestructiveIdempotent

Rename a list of the current user (the Lists of My games). Same as POST users/{idUser}/folders/{idFolder}/ with action=rename 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": {
      "folder": "<folder>",
      "name": "<name>"
    },
    "name": "rename_folder"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesNew name, at most 50 characters and different from the names of the other lists of the user.
folderYesId of the list, 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=false, idempotentHint=true and destructiveHint=true, so the mutation profile is covered. The description adds real value beyond them by disclosing the backing endpoint (POST .../action=rename) and where the result lands: the JSON body or error body is returned inside "response", which matters because there is no output schema.

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 purpose is front-loaded in a short first sentence, but the second sentence is a run-on that mixes the REST endpoint mapping with return-value behavior and reads awkwardly ("its JSON body, or its error body, comes in 'response'"). It is compact but not cleanly structured.

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?

For a two-parameter, fully documented mutation, the definition covers purpose, endpoint mapping, response envelope, and the id source. What is missing is error-handling detail beyond the mention of an error body and any permission/ownership constraints, which keeps it below a 5.

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 schema already explains both parameters, including the 50-character limit and the uniqueness constraint on the new name. The description adds only that the list belongs to the current user, so the baseline of 3 is 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 opens with a specific verb+resource ("Rename a list") and scopes it to the current user's lists ("Lists of My games"), which is enough to distinguish it from create_folder or delete_folders. It never explicitly names a sibling it competes with, so it falls short of the top mark.

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 only implied: you rename one of the current user's lists, and the folder id must come from list_my_folders (a useful procedural pointer). There is no explicit when-to-use vs. when-not guidance or comparison to alternatives like create_folder, so it sits at minimum viable.

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