Skip to main content
Glama
Sign In

Outil.io

by io.outil
OverviewDiscussionsAdmin

Insert slide

insert_slide

Insérer une diapositive après le rang after. Même contrat que les diapositives de create_presentation.

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>",
      "after": "<after>",
      "slide": "<slide>"
    },
    "name": "insert_slide"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesIdentifiant de la présentation (renvoyé par create_presentation ou list_presentations).
afterYesRang après lequel insérer (-1 : au début).
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

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and openWorldHint=true, so the mutation/safety profile is covered. The description adds that the slide payload follows the create_presentation contract, which is genuinely useful context beyond the annotations, but it says nothing about whether subsequent slides are renumbered after insertion or what the call returns.

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 short sentences with the insertion position front-loaded and no filler. It is arguably over-terse for a tool with a 90-value layout enum, but nothing is wasted.

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

Completeness3/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 should say what comes back after inserting a slide (new index, slide id, or nothing), and it does not. The reference to the create_presentation contract partially compensates for the complex nested payload, but the mutation's observable effects remain undocumented.

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 nested slide fields are documented in detail, including the -1 convention for 'after' and the null/absent image semantics. The description adds no meaning beyond that and merely restates the pointer to create_presentation that the schema already contains, so the baseline 3 applies.

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 names a specific verb and resource plus the insertion position ("Insérer une diapositive après le rang after"), which is more precise than the title alone. It does not distinguish the tool from close siblings such as add_slide_ai, update_slide or move_slide, so an agent must infer the difference from the names.

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

Usage Guidelines2/5

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

The only usage signal is an implicit one: the slide contract matches create_presentation, suggesting this tool is used to extend an existing presentation. There is no explicit statement of when to prefer this over add_slide_ai (AI-generated slide) or when to use update_slide instead, and no prerequisites or failure conditions are mentioned.

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