caisse-enregistreuse-mcp-server

Liste toutes les déclinaisons d’articles (par exemple : taille, couleur, grammage). Retourne un tableau d’objets indiquant les valeurs et écarts de prix éventuels.

data_list_variations

Read-only

Retrieve product variations from a sales recorder system in JSON, CSV, or HTML format to manage inventory and sales data.

Instructions

Liste des Lister les déclinaisons

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

Input Schema

Name	Required	Description	Default
`format`	No		json

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv1.0.0Jan 4, 2026
- addedInput schema / $schema
```
Added value: +"http://json-schema.org/draft-07/schema#"
```
- addedInput schema / additionalProperties
```
Added value: +false
```
First observedNov 12, 2025

TDQS

C2.2/5.0

Behavior3/5

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

The description adds no behavioral context beyond what annotations provide. Annotations indicate readOnlyHint=true, which the description does not contradict, but it also fails to disclose any additional traits like rate limits, authentication needs, or data scope. With annotations covering the safety profile, the description meets the baseline but adds no extra value.

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

Conciseness2/5

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

The description is overly concise to the point of being nonsensical ('Liste des Lister les déclinaisons'), which is not effective communication. It lacks structure and fails to convey useful information efficiently, making it under-specified rather than appropriately concise.

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

Completeness2/5

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

Given the tool's complexity (a list operation with price variation data) and lack of output schema, the description is incomplete. It does not explain what data is returned, how price differences are presented, or any limitations. With annotations only covering read-only status, the description fails to provide sufficient context for effective use.

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?

The description provides no information about parameters. With schema description coverage at 0%, the description does not compensate by explaining the 'format' parameter or its enum values. However, since there is only one optional parameter with a clear enum, the baseline score of 3 is appropriate as the schema handles the documentation adequately.

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

Purpose2/5

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

The description 'Liste des Lister les déclinaisons' is a tautology that essentially restates the tool name 'data_list_variations' in French, providing no meaningful elaboration on what the tool actually does. While the title offers more detail about listing article variations and returning price differences, the description itself fails to clarify the purpose beyond repeating the name.

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

Usage Guidelines1/5

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

The description provides no guidance on when to use this tool versus alternatives. It does not mention sibling tools like 'data_list_products' or specify contexts where this tool is appropriate, leaving the agent with no usage instructions.

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

Deploy Server