Skip to main content
Glama
Sign In

Outil.io

by io.outil
OverviewDiscussionsAdmin

Update slide

update_slide

Remplacer entièrement la diapositive de rang index (sa mise en page peut changer). Même contrat que les diapositives de create_presentation ; sans champ image, l’image actuelle est gardée.

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>",
      "index": "<index>",
      "slide": "<slide>"
    },
    "name": "update_slide"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesIdentifiant de la présentation (renvoyé par create_presentation ou list_presentations).
indexYesRang de la diapositive, à partir de 0 (0 = couverture).
slideYesUne diapositive : {layout, title, …champs de sa mise en page}. Les champs propres à chaque mise en page (steps, left/right, figure, quote, tableau, code, cas, roadmap, blocs, axes, centre, unite, legendes, quadrants…) sont décrits dans create_presentation.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

With annotations already declaring readOnlyHint=false and destructiveHint=false, the description earns credit by disclosing the replacement semantics: the whole slide is replaced, its layout may change, and omitting the image field preserves the existing image. The 'runs entirely' nature of the overwrite is important context an agent wouldn't get from annotations alone. It sits near the edge of destructiveHint=false but does not contradict it.

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?

Two dense sentences with the primary action front-loaded and the image-retention caveat placed after. Nothing is wasted, though the 'même contrat que create_presentation' clause forces the agent to consult another tool.

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 mutation tool with no output schema, the description covers the key behaviors: full replacement, possible layout change, and image retention. Because the nested slide schema is fully described, the remaining gap (what happens to fields omitted on a full replace) is minor.

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%, so the parameters are already well documented, including the image-null/absent behavior. The description adds only the cross-reference that the slide object follows the create_presentation contract, which is a useful hint but not new parameter meaning. Baseline 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?

States a precise verb+resource+scope: 'Remplacer entièrement la diapositive de rang index'. The word 'entièrement' and the note that layout may change distinguish it from partial edits like set_slide_image or rewrite_slide. It doesn't name a sibling explicitly, so it stops short of a 5.

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 by 'remplacer entièrement' – an agent can infer this is a full overwrite rather than a tweak, but no alternative is named and no condition selects between update_slide, rewrite_slide, or set_slide_image. The 'same contract as create_presentation slides' pointer helps the caller but is not when-to-use guidance.

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