Skip to main content
Glama
Sign In

Outil.io

by io.outil
OverviewDiscussionsAdmin

Rename presentation

rename_presentation

Renommer une présentation.

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": {
      "id": "<id>",
      "title": "<title>"
    },
    "name": "rename_presentation"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesIdentifiant de la présentation (renvoyé par create_presentation ou list_presentations).
titleYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

D1.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and openWorldHint=false, so the safety profile is partly covered. The description adds nothing beyond that — it does not say whether the change is immediate, whether the old title is lost, or what errors occur for an invalid id.

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?

One short, front-loaded sentence with no filler, so it is concise. However, brevity here comes from under-specification rather than tight writing, so it cannot score higher.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool is simple (2 required params, no output schema), but the description is silent on the mutation's effect, return value, and failure modes. It also switches to French while the tool name, title, and schema are English, which adds friction without adding information.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is only 50%: 'id' is documented but 'title' has no description, and the description supplies no semantics for either. It does not explain that title is the new name or that it is bounded to 1–191 characters.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Renommer une présentation" only restates the tool name and title in another language; it adds no scope, target, or distinguishing detail. It does not separate this operation from siblings such as get_presentation, update_slide, or set_presentation_theme.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use guidance, no mention of prerequisites (e.g. needing an existing presentation id), and no reference to alternatives. An agent must infer everything from the name alone.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Outil.io toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources