Skip to main content
Glama

Lire un test d'achat privé

lire_test
Read-onlyIdempotent

State and result of a private purchase test started with lancer_test (or paid per request with x402), by its id. No key needed: the id is the secret. Use it after lancer_test, every few minutes, until statut is termine or echec. For published results of tracked stores, use consulter_marchand instead. Returns: id, statut (en_attente, en_cours, termine or echec), domaine, produit, demande_le, commence_le, termine_le, dossier (private evidence report page: give this link to the user, it holds the screenshots, the proof of each fact and the log of the agent's actions), and once finished resultat: note (score out of 100), etapes (six steps, each reussi, partiel, echec or non_atteint with a motif), faits (oui, non or inconnu), lisibilite, captures and resume (one-sentence summary to quote). A failed test gives message and is not counted against the quota. Unknown id: error result.

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": {
      "id": "<id>"
    },
    "name": "lire_test"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesTest id returned by lancer_test: 48 hexadecimal characters.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description adds genuinely new behavior: no API key is required because the id itself is the secret, failed tests are not counted against the quota, and an unknown id returns an error result rather than throwing. It also enumerates the full returned payload including the private dossier evidence link the agent should hand to the user, which is operationally important context not available in any structured field.

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 cadence, then alternative, then return shape — a sensible ordering with no filler sentences. The return-field enumeration is dense and partly run-on, but each listed field carries information the agent needs given the absence of an output schema.

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?

With no output schema, the description correctly takes on the burden of describing every returned field, the async state machine (en_attente, en_cours, termine, echec), the polling cadence, the error case, and the quota caveat. Nothing an agent needs in order to call this and interpret its result is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and the schema already documents the lone parameter as 48 hexadecimal characters returned by lancer_test. The description adds meaning the schema does not: the id acts as the authorization secret, and an invalid id produces an error result. Marginal but real added value on top of a fully documented parameter.

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: reads the state and result of a private purchase test identified by its id. It immediately names the originating tool (lancer_test) and the sibling it is not (consulter_marchand), so an agent can distinguish it from other lookup tools without opening any schema.

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 explicit when-to-use: after lancer_test, polled every few minutes until statut is termine or echec. It also gives an explicit exclusion — for published results of tracked stores use consulter_marchand — and notes the x402 per-request paid variant, leaving no ambiguity about the alternative path.

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