Skip to main content
Glama
Sign In

Outil.io

by io.outil
OverviewDiscussionsAdmin

Set slide image

set_slide_image

Poser ou remplacer l’image d’une diapositive (url https téléchargée et rangée, ou asset du projet).

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

Input Schema

NameRequiredDescriptionDefault
idYesIdentifiant de la présentation (renvoyé par create_presentation ou list_presentations).
altNoCe que montre l’image.
urlNoAdresse https d’une image (par exemple un résultat de search_slide_images).
assetNoOu le chemin « /assets/u/… » d’une image déjà rangée.
indexYesRang de la diapositive, à partir de 0 (0 = couverture).
creditNoCrédit affiché (auteur, licence, page).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare this is a non-read-only, open-world, non-destructive write, so the baseline is lowered. The description does add real behavioral detail beyond them: a URL is downloaded and stored server-side, and an existing image on the slide is replaced. It says nothing about supported formats, size limits, or failure behavior when the URL cannot be fetched.

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?

A single compact sentence with the action front-loaded and the source options in a short parenthetical; nothing is wasted. It is compressed to the point of terseness, and the French phrasing in an otherwise English toolset slightly slows parsing.

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 six-parameter mutation tool with a fully described schema and a nested credit object, the description covers the action, the two input modes, and the replacement semantics. No output schema exists, but the tool returns nothing the agent must reason about, so no material gap remains.

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 every parameter is already documented in the schema and the baseline of 3 applies. The description adds the useful nuance that url and asset are alternative sources for the same slot, but it leaves alt and the nested credit object entirely to the schema.

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 gives a specific verb pair (poser/remplacer = set or replace) and a precise resource (l'image d'une diapositive), and it spells out the two accepted image sources. It stops short of naming sibling tools such as update_slide or insert_slide, so the agent must infer from the name alone which tool edits other slide properties.

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 call this when a slide needs an image, supplied either as an https URL or a project asset path. There is no explicit 'use X instead when…' routing, and no mention that search_slide_images or import_image_url typically precede this call, even though the sibling list makes those alternatives relevant.

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