Skip to main content
Glama
Sign In

Neoavis

by com.neoavis
OverviewDiscussionsAdmin

Trouver des marchands par critères

trouver_marchands
Read-onlyIdempotent

Discover French online stores where an AI agent can actually buy, filtered by PROVEN facts, in one sector or all of them. Use it when the user asks where to buy something online in France, which stores allow guest checkout, or which show the delivered price. To look up a store by name, use rechercher_marchand; for a whole sector ranking, classement_secteur. Every filter is optional; set a boolean to true to require that fact. Returns: secteur, criteres (filters applied), total (number of matching stores) and marchands, best score first, at most limite entries, each with rang, ex_aequo, secteur, domaine, nom, note out of 100, the five facts as booleans (sans_compte, prix_livre, frais_livraison, retours, ucp_commande), dernier_test and page. No match: total 0 and an empty list.

Input Schema

NameRequiredDescriptionDefault
ucpNoStore publishes a UCP profile that declares checkout, so an agent can order through the protocol.
langueNoLanguage of the page links and, for consulter_marchand, of the summary sentence: fr (default) or en. Data fields are the same in both.
limiteNoMaximum number of stores returned (default 20, at most 50); total still counts every match.
retoursNoReturn policy was found and quoted.
secteurNoRestrict to one sector; all sectors if omitted.
note_minNoMinimum score out of 100.
prix_livreNoTotal price including delivery was shown before any sign-up.
sans_compteNoAgent reached checkout without creating an account (proven by a screenshot or quote).
frais_livraisonNoShipping costs were found.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed9 schema fields changed
    • changedInput schema / properties / frais_livraison / description
      Previous value: -"Shipping costs found. / Frais de livraison trouvés."New value: +"Shipping costs were found."
    • addedInput schema / properties / langue / description
      Added 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."
    • addedInput schema / properties / limite
      Added value: +{
+  "description": "Maximum number of stores returned (default 20, at most 50); total still counts every match.",
+  "maximum": 50,
+  "minimum": 1,
+  "type": "integer"
+}
    • changedInput schema / properties / note_min / description
      Previous value: -"Minimum score out of 100. / Note minimale sur 100."New value: +"Minimum score out of 100."
    • changedInput schema / properties / prix_livre / description
      Previous value: -"Delivered price shown before any account. / Prix livré affiché avant tout compte."New value: +"Total price including delivery was shown before any sign-up."
    • changedInput schema / properties / retours / description
      Previous value: -"Return policy found. / Politique de retour trouvée."New value: +"Return policy was found and quoted."
    • changedInput schema / properties / sans_compte / description
      Previous value: -"Checkout without an account proven. / Commande sans compte prouvée."New value: +"Agent reached checkout without creating an account (proven by a screenshot or quote)."
    • changedInput schema / properties / secteur / description
      Previous value: -"Sector; all sectors if omitted. / Secteur, tous si absent."New value: +"Restrict to one sector; all sectors if omitted."
    • changedInput schema / properties / ucp / description
      Previous value: -"Publishes a UCP profile that declares checkout. / Profil UCP avec la commande."New value: +"Store publishes a UCP profile that declares checkout, so an agent can order through the protocol."
  2. Added

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world, so safety is cheap here; the description still adds real behavior: results sorted best-score-first, capped at limite, and the explicit no-match contract (total 0 plus empty list). It stops short of explaining how the score is computed or how freshness (dernier_test) affects ranking, which keeps it off a 5.

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 with purpose, then routing alternatives, then the return contract; no wasted sentences. The return enumeration is dense but earns its place because there is no output schema, though it is long enough to slightly dilute the routing message.

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 no output schema, the description carries the full return contract (secteur, criteres, total, marchands with rang/ex_aequo/note/five facts/page) and the empty-result case, which is exactly what an agent needs for 9 optional params. Minor gaps remain: it does not say how proven facts are missing vs false, nor whether the data is cached or how recent dernier_test must be.

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%, so the baseline is 3. The description does add one genuinely non-schema insight — that every filter is optional and a boolean true means 'require this proven fact' — but it otherwise restates the filter set rather than adding per-parameter meaning (e.g. how note_min interacts with unproven facts).

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 (discover/list) and resource (French online stores where an agent can buy), plus the filter-by-proven-facts scope. It explicitly names the siblings it is not (rechercher_marchand for name lookup, classement_secteur for a sector ranking), so an agent can route without opening other schemas.

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 scenarios ('where to buy something online in France', 'which stores allow guest checkout', 'which show the delivered price') and pairs each sibling name with the condition that selects it. It also states all filters are optional and that a boolean set to true is a requirement, which removes the main usage ambiguity.

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

All Neoavis toolsInspect
Try in Browser
Let your AI agent see the webWeb-to-screenshot MCP for Claude, Cursor and Codex. No cookie banners. Free to start.snap-render.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources