Skip to main content
Glama
fauguste

boondmanager-mcp-server

by fauguste
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Détails d'un positionnement

boond_positionings_get
Read-onlyIdempotent

Retrieve the complete record of a specific positioning by its numeric ID, including attributes and relations not shown in search summaries. Use after a search to get full details for a known ID.

Instructions

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

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

  • Un ID inconnu remonte l'erreur BoondManager telle quelle — l'ID doit venir de boond_positionings_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é BoondManager (numérique)

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. Changed3 schema fields changedv2.7.0
    • changedInput schema / properties / id / description
      Previous value: -"Identifiant unique de l'entité BoondManager"New value: +"Identifiant unique de l'entité BoondManager (numérique)"
    • removedInput schema / properties / id / minLength
      Removed value: -1
    • addedInput schema / properties / id / pattern
      Added value: +"^\\d+$"
  3. First observedv2.1.0

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already cover readOnly, idempotent, and non-destructive hints. The description adds meaningful behavioral advice: unknown IDs surface the BoondManager error as is, so the ID must be sourced from search and never guessed. It also specifies the return shape as JSON attributes + relations, which goes beyond the structural annotations and helps the agent understand the response even without a formal output schema.

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?

The definition begins with a lead purpose sentence, then moves to usage guidance, then to input constraint, and ends with the return description. Every part contributes value. Minor redundancy: the final 'Lecture seule' repeats the annotation's readOnlyHint, which is not necessary but costs no harm. The structure also uses French labels in a natural way for front-loaded clarity.

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 single-parameter, read-only getter, the description is complete: it gives the call context (after search), the ID source, the error scenario, and the return type. No output schema exists, so the description's statement of 'JSON de l'entité' fills that gap. There is nothing an agent needs to know about correct invocation that 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?

The schema already documents the id parameter fully (pattern, type, description at 100% coverage). The description elevates this with contextual semantics: the ID is not merely any fee but comes from boond_positionings_search, and the tool refuses name-based lookups. This adds actionable knowledge beyond the schema fields.

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 states a clear verb (Récupère), a specific resource (la fiche complète d'un positionnement), and the attribute ID (par son ID numérique). It differentiates itself from its sibling search tool by explicitly noting it provides attributes not in the list summary, making it unambiguous against boond_positionings_search, create, update, and delete.

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 describes when to use the tool: after a boond_positionings_search when full attributes are needed. It names the alternative (`boond_positionings_search`) and states the condition for choosing that alternative (if the ID is not known). It also warns that this tool does not accept a name, giving clear selection guidance.

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