Skip to main content
Glama

Scores and offers of one model

fiche_modele
Read-onlyIdempotent

Scores (overall and per buyer profile), per-criterion scores, selected new and refurbished offers, for one model found by name (e.g. "Galaxy S25", "iPhone 16 Pro").

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>",
      "modele": "<modele>"
    },
    "name": "fiche_modele"
  }
}

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.
modeleYesModel name, brand optional.
categorieYesProduct category page: telephones = smartphones, tablettes = tablets, ordinateurs-portables = laptops, montres-connectees = smartwatches, montres-sport = sport watches.

Output Schema

NameRequiredDescriptionDefault
anneeYes
ficheYesPicksly page of the model, explaining how its scores are calculated.
notesYes
deviseYes
marcheYes
marqueYes
modeleYes
offresYes
mentionYesAffiliate disclosure.
criteresYesPer-criterion scores 0–100 (performance, battery…).
remarqueNo
categorieYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "annee": {
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "categorie": {
      +      "type": "string"
      +    },
      +    "criteres": {
      +      "additionalProperties": {
      +        "type": "number"
      +      },
      +      "description": "Per-criterion scores 0–100 (performance, battery…).",
      +      "type": "object"
      +    },
      +    "devise": {
      +      "type": "string"
      +    },
      +    "fiche": {
      +      "description": "Picksly page of the model, explaining how its scores are calculated.",
      +      "type": "string"
      +    },
      +    "marche": {
      +      "type": "string"
      +    },
      +    "marque": {
      +      "type": "string"
      +    },
      +    "mention": {
      +      "description": "Affiliate disclosure.",
      +      "type": "string"
      +    },
      +    "modele": {
      +      "type": "string"
      +    },
      +    "notes": {
      +      "properties": {
      +        "budget": {
      +          "description": "Score 0–100, null when not enough is measured.",
      +          "type": [
      +            "number",
      +            "null"
      +          ]
      +        },
      +        "globale": {
      +          "description": "Score 0–100, null when not enough is measured.",
      +          "type": [
      +            "number",
      +            "null"
      +          ]
      +        },
      +        "premium": {
      +          "description": "Score 0–100, null when not enough is measured.",
      +          "type": [
      +            "number",
      +            "null"
      +          ]
      +        },
      +        "smart": {
      +          "description": "Score 0–100, null when not enough is measured.",
      +          "type": [
      +            "number",
      +            "null"
      +          ]
      +        }
      +      },
      +      "required": [
      +        "globale",
      +        "budget",
      +        "smart",
      +        "premium"
      +      ],
      +      "type": "object"
      +    },
      +    "offres": {
      +      "items": {
      +        "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"
      +      },
      +      "type": "array"
      +    },
      +    "remarque": {
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "categorie",
      +    "marche",
      +    "devise",
      +    "marque",
      +    "modele",
      +    "annee",
      +    "notes",
      +    "criteres",
      +    "offres",
      +    "fiche",
      +    "mention"
      +  ],
      +  "type": "object"
      +}
  2. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description contributes the scope of data returned and the 'found by name' lookup semantics, but with an output schema present it does not need to (and does not) add much beyond that.

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?

A single dense sentence with zero filler; the returned content is front-loaded before the input constraint, and every clause carries information. Nothing to trim.

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 a full input schema, an output schema, and four annotations, the description supplies enough for correct invocation. The only gap is the absence of disambiguation against the two sibling tools, which keeps it from being fully complete.

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 each parameter is already documented, so the baseline is 3. The description adds value by giving real model-name examples ('Galaxy S25', 'iPhone 16 Pro') that clarify how loosely the modele field should be filled, but it adds nothing about categorie or pays.

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 ('fiche'/sheet for one model) and enumerates its contents: overall and per-buyer-profile scores, per-criterion scores, and selected new/refurbished offers, with concrete model-name examples. It does not, however, contrast itself with the sibling tools comparer_modeles or meilleurs_choix, so the agent must infer that this is the single-model lookup.

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

Usage Guidelines2/5

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

The phrase 'for one model found by name' implies a single-model lookup and the examples show the expected input format, but there is no explicit statement of when to use this versus comparer_modeles (multi-model) or meilleurs_choix (best picks). No prerequisites or exclusions are stated.

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