Skip to main content
Glama
Sign In
viraldar

viraldar

by ThomasRayvol
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Modèles de carrousel

carrousel_modeles
Read-only

Lists TikTok carousel templates with purpose, fields, default theme, JSON example, and safe zones for 9:16, 3:4, and 4:5 formats so you can pick and render the right layout before writing.

Instructions

Liste les modèles de carrousel TikTok (citation, liste, notes, contraste, ecran, revelation, natif) : à quoi chacun sert, les champs qu'il lit, son thème par défaut et un exemple de JSON complet à passer à carrousel_rendre ; et les formats (9:16, 3:4, 4:5) et les zones sûres par cas (avec ou sans description, pub), avec leur source. À appeler avant d'écrire un carrousel. Avec modele, ne donne que celui-là.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "carrousel_modeles"
  }
}

Input Schema

NameRequiredDescriptionDefault
modeleNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, so safety is covered; the description goes further by disclosing the shape of the payload — per-template purpose, fields read, default theme, a full JSON example, plus formats and safe zones with their source. That is substantive content disclosure beyond the annotations, though it says nothing about response size or how the source citations are formatted.

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?

Front-loaded with verb and resource, then a single dense clause enumerating the returned fields, then two short routing sentences. Every clause carries information, though the parenthetical catalog and the long enumeration make the first sentence heavy.

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 read-only reference tool with one optional enum parameter and no output schema, the description covers what is returned, when to call it, the effect of the filter, and where its data flows next (carrousel_rendre). Nothing an agent needs in order to call it correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, but the single parameter is an enum whose seven values are spelled out in the description, and the description explains the behavioral effect of supplying it (return only that one template instead of the whole catalog). That is meaning beyond the bare enum list, though it does not say what happens for an invalid value or whether the default is the full catalog.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Opens with a specific verb and resource ("Liste les modèles de carrousel TikTok"), enumerates the seven template names, and states exactly what is returned for each (purpose, fields read, default theme, complete JSON example). It also names the downstream consumer carrousel_rendre, so the agent can place it relative to a sibling without opening any schema.

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

Usage Guidelines4/5

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

Gives an explicit trigger: "À appeler avant d'écrire un carrousel", which tells the agent the ordering relative to carrousel_rendre. It also explains the filtered mode ("Avec `modele`, ne donne que celui-là"). There is no explicit when-not case, but for a pure reference catalog none is really needed.

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

Deploy Server

Other Tools