Skip to main content
Glama
fauguste

boondmanager-mcp-server

by fauguste
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Détails d'un(e) produit

boond_products_get
Read-onlyIdempotent

Retrieve complete product details by ID. Use after a product search to access full attributes, optional tab-specific sections like technical data. Requires a valid numeric ID from search results.

Instructions

Récupère la fiche complète d'un(e) produit par son ID numérique.

Quand : après un boond_products_search, pour obtenir les attributs qui n'apparaissent pas dans le résumé de liste. Plutôt que : boond_products_search si l'ID n'est pas connu (cet outil n'accepte pas de nom).

  • tab cible un onglet précis (information, technical-data, administrative, actions…) ; sans tab, seule la fiche de base est renvoyée, pas la réunion des onglets.

  • Un ID inconnu remonte l'erreur BoondManager telle quelle — l'ID doit venir de boond_products_search, jamais d'une supposition.

Returns : JSON de l'entité (attributs + relations) tel que renvoyé par l'API. Lecture seule.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesIdentifiant unique de l'entité (numérique)
tabNoOnglet spécifique à récupérer (information, technical, financial, actions, contracts, documents)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.12.2
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
  2. Changed4 schema fields changedv2.7.0
    • changedInput schema / properties / id / description
      Previous value: -"Identifiant unique de l'entité"New value: +"Identifiant unique de l'entité (numérique)"
    • removedInput schema / properties / id / minLength
      Removed value: -1
    • addedInput schema / properties / id / pattern
      Added value: +"^\\d+$"
    • addedInput schema / properties / tab / pattern
      Added value: +"^[a-zA-Z][a-zA-Z-]*$"
  3. First observedv2.1.0

TDQS

A5/5.0
Behavior5/5

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

Beyond the annotations (readOnlyHint, idempotentHint, destructiveHint false), the description discloses that omitting tab returns only the base fiche, not a union of tabs, and that an unknown ID surfaces the raw BoondManager error. It also explicitly states 'Lecture seule', consistent with the annotations.

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 well structured with a core one-liner, labeled 'Quand' and 'Plutôt que' sections, bullets for parameter behavior, and a short Returns note. Every sentence adds value, and the most important routing information is front-loaded.

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?

For a get-by-id tool with no output schema, it covers what the tool returns (entity JSON with attributes and relations), how to obtain a valid id, what happens on unknown ids, and the optional tab behavior. Nothing essential for correct invocation is missing.

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

Parameters5/5

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

Schema coverage is 100%, and the description adds meaningful semantics on top: tab selects a specific tab with examples and a default-behavior caveat, and id is constrained to IDs obtained from search rather than guessed. This materially helps an agent pass correct values.

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?

The description opens with a specific verb and resource: 'Récupère la fiche complète d'un produit par son ID numérique.' It clearly differentiates this get-detail tool from boond_products_search by noting it fetches attributes absent from the list summary and only accepts an ID, not a name.

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?

It explicitly states when to use the tool ('après un boond_products_search') and when not to ('Plutôt que : boond_products_search si l'ID n'est pas connu'), naming the alternative and the condition that selects it. The tab guidance also clarifies optional usage.

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