Skip to main content
Glama

Top-rated models for a buyer profile

meilleurs_choix
Read-onlyIdempotent

Highest-rated models of a category for a buyer profile and an optional maximum budget, with current price, merchant, purchase link and the Picksly page explaining the score.

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": {
      "categorie": "<categorie>"
    },
    "name": "meilleurs_choix"
  }
}

Input Schema

NameRequiredDescriptionDefault
paysNoISO country code of the buyer (FR, US, GB, DE, ES, IT, NL, BE, PT, and most others mapped to the nearest store). Default FR.
langueNoLanguage of the Picksly page links. Default: the page decides.
nombreNoHow many models (default 3).
profilNobudget, smart (default) or premium.
categorieYesProduct category page: telephones = smartphones, tablettes = tablets, ordinateurs-portables = laptops, montres-connectees = smartwatches, montres-sport = sport watches.
budget_maxNoMaximum price in the market currency.
reconditionneNoOnly refurbished offers.

Output Schema

NameRequiredDescriptionDefault
deviseYes
marcheYes
profilYes
mentionYesAffiliate disclosure.
modelesYes
remarqueNo
categorieYes
budget_maxYes
classement_completYesPicksly page with the full ranking.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "budget_max": {
      +      "type": [
      +        "number",
      +        "null"
      +      ]
      +    },
      +    "categorie": {
      +      "type": "string"
      +    },
      +    "classement_complet": {
      +      "description": "Picksly page with the full ranking.",
      +      "type": "string"
      +    },
      +    "devise": {
      +      "type": "string"
      +    },
      +    "marche": {
      +      "type": "string"
      +    },
      +    "mention": {
      +      "description": "Affiliate disclosure.",
      +      "type": "string"
      +    },
      +    "modeles": {
      +      "items": {
      +        "properties": {
      +          "annee": {
      +            "type": [
      +              "string",
      +              "null"
      +            ]
      +          },
      +          "fiche": {
      +            "type": [
      +              "string",
      +              "null"
      +            ]
      +          },
      +          "marque": {
      +            "type": "string"
      +          },
      +          "modele": {
      +            "type": "string"
      +          },
      +          "note_globale": {
      +            "description": "Score 0–100, null when not enough is measured.",
      +            "type": [
      +              "number",
      +              "null"
      +            ]
      +          },
      +          "note_profil": {
      +            "type": "number"
      +          },
      +          "offre": {
      +            "properties": {
      +              "devise": {
      +                "type": "string"
      +              },
      +              "etat": {
      +                "description": "neuf = new, reconditionne = refurbished.",
      +                "enum": [
      +                  "neuf",
      +                  "reconditionne"
      +                ],
      +                "type": "string"
      +              },
      +              "lien_achat": {
      +                "description": "Affiliate link to the store page, through picksly.fr.",
      +                "type": "string"
      +              },
      +              "marchand": {
      +                "description": "Store selling the offer.",
      +                "type": "string"
      +              },
      +              "prix": {
      +                "type": "number"
      +              },
      +              "prix_releve_le": {
      +                "description": "Date (YYYY-MM-DD) the price was last read at the store.",
      +                "type": [
      +                  "string",
      +                  "null"
      +                ]
      +              }
      +            },
      +            "required": [
      +              "etat",
      +              "prix",
      +              "devise",
      +              "marchand",
      +              "prix_releve_le",
      +              "lien_achat"
      +            ],
      +            "type": [
      +              "object",
      +              "null"
      +            ]
      +          },
      +          "rang": {
      +            "type": "integer"
      +          }
      +        },
      +        "required": [
      +          "rang",
      +          "marque",
      +          "modele",
      +          "annee",
      +          "note_profil",
      +          "note_globale",
      +          "offre",
      +          "fiche"
      +        ],
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    "profil": {
      +      "enum": [
      +        "budget",
      +        "smart",
      +        "premium"
      +      ],
      +      "type": "string"
      +    },
      +    "remarque": {
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "categorie",
      +    "profil",
      +    "marche",
      +    "devise",
      +    "budget_max",
      +    "modeles",
      +    "classement_complet",
      +    "mention"
      +  ],
      +  "type": "object"
      +}
  2. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is fully covered. The description adds that results are ranked by a score and include price, merchant, purchase link and an explanatory Picksly page – meaningful ranking semantics, but the return payload is also documented by the output schema, so the marginal value is modest.

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 that names the resource first and the qualifiers and return contents after. No filler, though it packs the return-value list into the same sentence rather than prioritizing the ranking criterion.

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 7 params (1 required), full schema coverage, annotations and an output schema, the description covers purpose, key qualifiers and result contents adequately. The remaining gap is sibling routing and the interaction between profile and budget filters, which an agent must guess.

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 enums are self-documenting, so the schema does the heavy lifting. The description only echoes category, profile and budget at a high level, adding no format, default, or interaction detail (e.g. how budget_max interacts with profil=budget) 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 names a specific resource (highest-rated models within a category) plus the qualifying dimensions (buyer profile, optional max budget) and the returned fields. This clearly separates it from fiche_modele (single model detail) and comparer_modeles (comparison), though it never names those siblings 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?

Usage is implied by 'of a category for a buyer profile' – an agent can infer this is the category-browsing/recommendation tool. However, there is no explicit when-to-use/when-not guidance and no reference to comparer_modeles or fiche_modele, so routing between the three siblings is left to inference.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources