Skip to main content
Glama

Incarn

by co.incarn

Exemples d'animations

list_examples
Read-only

Voir des exemples avant/après d'animation de photos anciennes (galerie de démonstration).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
beatNoThème optionnel (ex: 'mariage', 'bébé', 'portrait').

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
beatYesThème appliqué, ou null.
examplesYesListe d'exemples avant/après.
gallery_urlYesURL de la galerie publique où chaque portrait s'anime (avant/après). À partager avec l'utilisateur.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed2 schema fields changed
    • addedOutput schema / properties / gallery_url
      Added value: +{
+  "description": "URL de la galerie publique où chaque portrait s'anime (avant/après). À partager avec l'utilisateur.",
+  "type": "string"
+}
    • changedOutput schema / required
      Previous value: -[
-  "beat",
-  "examples"
-]New value: +[
+  "beat",
+  "gallery_url",
+  "examples"
+]
  2. Changed4 schema fields changed
    • changedOutput schema / properties / examples / items / properties / thumbnail_url / description
      Previous value: -"URL de la photo d'origine (avant)."New value: +"URL de la vignette."
    • removedOutput schema / properties / examples / items / properties / video_url
      Removed value: -{
-  "description": "URL de la vidéo animée (après).",
-  "type": "string"
-}
    • removedOutput schema / properties / examples / items / properties / year
      Removed value: -{
-  "description": "Année de la photo d'origine.",
-  "type": "string"
-}
    • changedOutput schema / properties / examples / items / required
      Previous value: -[
-  "title",
-  "year",
-  "thumbnail_url",
-  "video_url"
-]New value: +[
+  "title",
+  "thumbnail_url"
+]
  3. Changed4 schema fields changed
    • changedOutput schema / properties / examples / items / properties / thumbnail_url / description
      Previous value: -"URL de la vignette."New value: +"URL de la photo d'origine (avant)."
    • addedOutput schema / properties / examples / items / properties / video_url
      Added value: +{
+  "description": "URL de la vidéo animée (après).",
+  "type": "string"
+}
    • addedOutput schema / properties / examples / items / properties / year
      Added value: +{
+  "description": "Année de la photo d'origine.",
+  "type": "string"
+}
    • changedOutput schema / properties / examples / items / required
      Previous value: -[
-  "title",
-  "thumbnail_url"
-]New value: +[
+  "title",
+  "year",
+  "thumbnail_url",
+  "video_url"
+]
  4. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "beat": {
+      "description": "Thème appliqué, ou null.",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "examples": {
+      "description": "Liste d'exemples avant/après.",
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "thumbnail_url": {
+            "description": "URL de la vignette.",
+            "type": "string"
+          },
+          "title": {
+            "description": "Titre de l'exemple.",
+            "type": "string"
+          }
+        },
+        "required": [
+          "title",
+          "thumbnail_url"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "beat",
+    "examples"
+  ],
+  "type": "object"
+}
  5. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already mark this as read-only and non-destructive, and the description does not contradict them. It adds the 'before/after example gallery' context but does not disclose additional behaviors such as default unfiltered listing, pagination, or how the optional theme affects results.

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?

The description is a single, focused sentence with no filler. It front-loads the action and resource, and the parenthetical clarifies the nature of the tool effectively.

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 simple read-only demonstration tool with full annotation coverage, an output schema, and one well-documented optional parameter, the description is nearly complete. It could explicitly say that 'beat' filters the examples, but the schema already covers that, so the gap 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%, and the single optional parameter 'beat' is already explained with examples in the schema. The tool description adds no additional semantic detail about the parameter, so the baseline of 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?

The description states a clear verb and resource: 'Voir des exemples avant/après d'animation de photos anciennes' (see before/after examples). It also labels itself as a demonstration gallery, which sets it apart from the upload/processing siblings even though it does not name any sibling explicitly.

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?

The 'galerie de démonstration' framing implies it is meant for previewing examples, presumably before animating a photo, but the description does not explicitly say when to use it versus the sibling tools. Usage context is implied rather than stated.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Incarn toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4/5.0
Disambiguation4/5

Each tool targets a distinct stage of the animation workflow—main action, upload steps, status polling, and examples—and the descriptions cross-reference each other explicitly. Minor ambiguity exists between animate_photo and create_upload as alternative entry points, but the 'prefer image_url' guidance effectively resolves it.

Naming Consistency5/5

All five tools follow a consistent verb_noun snake_case pattern (animate_photo, create_upload, confirm_upload, get_animation_status, list_examples), using clear, predictable verbs throughout. There is no mixing of conventions or vague generic names.

Tool Count4/5

Five tools is well-scoped for the narrow domain of photo animation, with the two upload steps adding necessary surface area for the file-attachment path. Slightly heavy for such a niche service, but each tool earns its place.

Completeness4/5

The core lifecycle is fully covered: upload a photo, animate it, poll status, and view examples. Minor gaps include no credit-balance check despite animation being credit-gated, and no way to list past animations or recover a lost job ID.

Resources