Skip to main content
Glama
Sign In

Outil.io

by io.outil
OverviewDiscussionsAdmin

Set presentation theme

set_presentation_theme

Changer le modèle visuel (et la personnalisation) : les diapositives sont remises en page sans IA ; une diapositive retouchée à la main garde ses blocs.

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

Input Schema

NameRequiredDescriptionDefault
idYesIdentifiant de la présentation (renvoyé par create_presentation ou list_presentations).
themeYesIdentifiant d’un modèle (list_slide_themes).
customizationNoCouleurs #rrggbb (fond, encre, accent, accent2), polices et taille du texte par-dessus le modèle ; null : aucune.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already state this is a non-read-only but non-destructive write, so the description is not carrying the safety burden alone. It still adds real behavioral context beyond the annotations: slides are re-laid out without AI, and manually edited slides retain their blocks rather than being flattened. That tells the agent exactly what side effects to expect on existing content.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single compact sentence, front-loaded with the action and followed by the two consequences (non-AI re-layout, preservation of hand-edited blocks). No filler; every clause carries information.

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?

With three parameters, full schema documentation and no output schema, the description covers the essential unknown — what happens to existing slide content. It could go slightly further on whether an invalid theme id fails or silently no-ops, but nothing critical is missing for correct invocation.

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 schema already explains id, theme (an identifier from list_slide_themes) and the customization object. The description only gestures at customization via the parenthetical '(et la personnalisation)' and adds no new meaning about how customization overlays the theme — 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+resource pair ('Changer le modèle visuel' plus customization) and clarifies that the target is slide layout, which separates it from slide-level siblings like update_slide or insert_slide. It stops short of naming a contrasting sibling or listing when a different theme-related tool (e.g. list_slide_themes) should be used instead.

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 implied rather than stated: the agent can infer this applies a theme to an existing presentation, and the note about hand-edited slides is a useful caveat. There is no explicit when-to-use/when-not guidance and no pointer to the alternative of per-slide edits (update_slide) when the agent only wants cosmetic changes on one slide.

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