Skip to main content
Glama
Sign In
lbc-mcp

lbc-mcp

by BPiroga
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Profil d'un vendeur Leboncoin

get_seller
Read-only

Fetch a Leboncoin seller's profile: tenure, rating, review count, response rate and time, active listings, and professional shop details like SIRET, address, and website.

Instructions

Profil d'un vendeur : anciennete, note sur 5 et nombre d'avis, taux et delai de reponse, nombre d'annonces en ligne, et pour un professionnel sa boutique (SIRET, adresse, site web).

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": {
      "seller": "<seller>"
    },
    "name": "get_seller"
  }
}

Input Schema

NameRequiredDescriptionDefault
sellerYesseller_id renvoye par get_ad, ou identifiant/URL d'une annonce du vendeur.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is established. The description adds the payload contents and the conditional professional-shop field, which is useful but does not disclose behavior for edge cases such as unknown sellers or missing professional data. With annotations covering the main behavior, a 3 is appropriate.

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?

The description is a single, compact sentence that front-loads the purpose and then lists the returned fields in a clear semicolon-separated structure. Every word earns its place and there is no filler.

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?

For a one-parameter read-only lookup with full schema coverage and an output schema present, the description is largely complete. It covers the returned data well and the parameter description implies how to obtain the seller identifier. Explicit routing from get_ad could improve it, but is not a significant gap.

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 single seller parameter is well documented in the schema as the seller_id from get_ad or an ad identifier/URL. The description itself adds no extra parameter-level meaning, so the baseline of 3 applies.

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 clearly identifies the resource ('Profil d'un vendeur') and enumerates the specific data returned: anciennete, note, avis, response metrics, active listings, and professional shop details. It is distinguishable from get_ad and search_ads because it focuses on seller-level profile data rather than ads or searches, though it lacks an explicit action verb.

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?

There is no explicit when-to-use or when-not-to-use statement. However, the schema's parameter description says the seller is a seller_id returned by get_ad or an ad URL, which implies this is the follow-up tool for seller-level information. The usage context is present but not made explicit.

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

Deploy Server

Other Tools