Skip to main content
Glama

Consulter un marchand

consulter_marchand
Read-onlyIdempotent

Full test result for ONE French online store, by domain: what an AI shopping agent managed to do there at the latest test. Use it before visiting, recommending or buying from a French store, or when the user asks if a store works with AI agents. To find stores you do not know yet, use trouver_marchands; to look up a store by name, rechercher_marchand; to put several side by side, comparer_marchands. Returns: note (score out of 100: journey 55, proven purchase facts 30, machine readability 15), etapes (six steps in order — acces, cookies, recherche, fiche, panier, caisse — each reussi, partiel, echec or non_atteint, with a motif when it failed), faits (oui, non or inconnu: checkout without an account, delivered price before sign-up, shipping costs, return policy, third-party seller), machine (product data, robots.txt, llms.txt, sitemap, UCP), ucp_commande (store declares UCP checkout), dernier_test (date), test_ancien (true if older than 90 days), resume (one-sentence summary to quote) and page (link to cite). Unknown or untracked domain: error result, nothing charged, with suites_payantes when available (x402 URLs to check that store live or have it fully tested) and test_prive_agence (the Agency plan: a private full purchase test of that store with lancer_test).

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": {
      "domaine": "<domaine>"
    },
    "name": "consulter_marchand"
  }
}

Input Schema

NameRequiredDescriptionDefault
langueNoLanguage of the page links and, for consulter_marchand, of the summary sentence: fr (default) or en. Data fields are the same in both.
domaineYesStore domain, for example respire.co. A full URL or a www. prefix is accepted and normalised.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / domaine / description
      Previous value: -"Merchant domain, for example exemple-beaute.fr. A full URL is accepted. / Domaine du marchand, adresse complète acceptée."New value: +"Store domain, for example respire.co. A full URL or a www. prefix is accepted and normalised."
    • changedInput schema / properties / langue / description
      Previous value: -"Language of the summary sentence and of the page link (default fr)."New value: +"Language of the page links and, for consulter_marchand, of the summary sentence: fr (default) or en. Data fields are the same in both."
  2. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the description's job is context — and it delivers: unknown or untracked domains return an error result with 'nothing charged', plus upsell branches (suites_payantes x402 URLs, test_prive_agence via lancer_test). It also discloses staleness semantics (test_ancien true if older than 90 days) and that data may be a partial/state snapshot rather than a live crawl.

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 correctly: purpose first, then usage and alternatives, then the return contract, then error/upsell behaviour. It is dense and long, but since there is no output schema the return enumeration earns its space; a few clauses (ucp_commande, page citation) could be tightened.

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?

No output schema exists, so the description carries the full return contract, and it does: the composite score breakdown (55/30/15), the six ordered steps with their status values, the fact fields, machine-readability signals, freshness flag, quotable resume and citation page. An agent can both decide to call it and interpret its output without further help.

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 coverage is 100% and both parameters are fully documented in the schema, including the langue enum and domain normalisation. The description only says 'by domain' and adds nothing about format or language behaviour beyond what the schema states, so baseline 3 applies.

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?

States a specific verb and resource with explicit scope: 'Full test result for ONE French online store, by domain' plus what the result reflects ('what an AI shopping agent managed to do there at the latest test'). The word 'ONE' and the sibling list make it unmistakable versus comparer_marchands or rechercher_marchand.

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

Usage Guidelines5/5

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

Gives concrete trigger conditions ('before visiting, recommending or buying from a French store, or when the user asks if a store works with AI agents') and explicitly routes three alternatives: trouver_marchands for discovery, rechercher_marchand for name lookup, comparer_marchands for side-by-side comparison. When-to-use and when-to-use-something-else are both covered.

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