Skip to main content
Glama
Sign In
viraldar

viraldar

by ThomasRayvol
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Modifier Mes thèmes

modifier_mes_themes

Add, remove, or replace themes (infos_base keys) in a user's “Mes thèmes” list; change this shared list only when the user explicitly asks.

Instructions

Ajoute ou retire des thèmes (clés de infos_base) dans « Mes thèmes » de l'utilisateur, ou les remplace tous. C'est la même liste que sur le site : ne la change que si l'utilisateur le demande.

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": "modifier_mes_themes"
  }
}

Input Schema

NameRequiredDescriptionDefault
ajouterNo
retirerNo
remplacerNoLa liste complète, à la place de l'actuelle.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations at all, the description carries the full behavioral burden. It usefully discloses that this mutates persistent, user-visible state shared with the site, which is the most important risk here. It does not say what happens when `ajouter`/`retirer`/`remplacer` are combined, whether changes are reversible, or what permissions/identity are required.

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?

Two tight sentences, front-loaded with the capability and followed by the guardrail. Nothing redundant, and the mutation-versus-replacement distinction is stated up front.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a three-parameter mutation tool with no annotations and no output schema, the description covers purpose, persistence, and a caution, which is the essential core. It stops short of covering parameter interactions, required identity, and the resulting state after the call, so an agent could still call it incorrectly in edge cases.

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 only 33% (only `remplacer` is annotated), so the description must compensate, and it largely does: it maps the three operations to add/remove/replace-all and defines themes as `infos_base` keys, which the schema never says. It falls short on interaction semantics — mutual exclusivity and precedence between `remplacer` and the incremental parameters are unstated.

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: add, remove, or fully replace themes inside the user's « Mes thèmes ». It also clarifies the unit of work — themes are keys from `infos_base` — which makes the scope concrete. It does not name the read sibling `mes_themes`, so the distinction from a listing tool is left implicit.

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?

There is an explicit when-not rule: only change the list if the user asks, since it is the same list visible on the site. That is a real guardrail against speculative mutation. What is missing is an explicit pointer to `mes_themes` for reading the current list before deciding what to add or remove.

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