Skip to main content
Glama
Sign In

Outil.io

by io.outil
OverviewDiscussionsAdmin

Rewrite slide

rewrite_slide

Faire réécrire une diapositive par l’assistant de l’outil selon une consigne (la mise en page peut changer ; son image est gardée sauf si la consigne en parle).

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>",
      "instruction": "<instruction>"
    },
    "name": "rewrite_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).
instructionYesCe qu’il faut changer (« plus concret », « en tableau », « ajoute les chiffres de 2024 »…) ; vide : l’améliorer.

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?

Annotations already declare write (readOnlyHint=false), non-destructive, and open-world, but the description adds genuinely useful behavioral facts not present in structured data: the layout may change and the slide's existing image is preserved unless the instruction explicitly mentions it. It does not say whether the operation is synchronous, costly, or what it returns, which keeps it below a 5.

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 front-loaded sentence with the core action first and a parenthetical qualifying the two side effects. Compact with no filler, though the parenthetical is dense and slightly hard to parse on first read.

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 fully documented required parameters, annotations covering the safety profile, and no output schema, the description covers the main behavioral surprises (layout change, image retention). It stops short of stating the result shape or whether the slide content is replaced wholesale versus merged, which matters for a rewrite operation.

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 all three parameters (id, index, instruction) are already documented, including the note that an empty instruction means 'improve it'. The description only echoes 'selon une consigne' and adds no format, length, or language constraints beyond what the schema states.

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 states a specific verb and resource ('faire réécrire une diapositive') and names the actor doing it ('par l'assistant de l'outil'), which separates it from a plain field-level update. It does not explicitly name the sibling it replaces (update_slide) or the generation sibling (add_slide_ai), so differentiation is implied rather than stated.

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: an agent can infer this is the tool for AI-driven content revision rather than manual editing, but there is no explicit 'use this when…, use update_slide instead when…' guidance. No prerequisites or exclusions are given.

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