Skip to main content
Glama
fauguste

boondmanager-mcp-server

by fauguste
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Mettre à jour le dossier technique d'une ressource

boond_resources_technical_data_update
Idempotent

Update a resource's technical profile (skills, tools, languages, diplomas, experience). Merge mode adds missing items; replace mode overwrites only provided fields.

Instructions

Met à jour le dossier technique (DT) d'une ressource : compétences, outils, langues, expertises, formations, diplômes, expérience.

Quand : pour mettre à jour le dossier technique d'une ressource (compétences, formations, langues…). Plutôt que : boond_resources_reference_create / _update / _delete pour les seules expériences professionnelles : elles vivent dans le même bloc, mais ces outils évitent d'avoir à republier le tableau entier.

Mode 'merge' (défaut, recommandé pour automation) — enrichit sans rien écraser : • skills (CSV) : concatène les compétences absentes • tools / languages : ajoute les entrées dont la clé (slug outil / langue) est nouvelle, conserve le niveau existant pour les autres • expertiseAreas, activityAreas, diplomas : ajoute les items absents • title, summary, training, experience : remplis UNIQUEMENT si actuellement vides

Mode 'replace' — remplace intégralement chaque champ fourni par la valeur passée. Les champs non passés ne sont pas touchés.

Seuls les champs explicitement fournis dans l'appel sont envoyés à l'API — un champ omis ne sera jamais réinitialisé à vide.

Les expériences professionnelles (références) ne sont PAS gérées ici : utiliser boond_resources_reference_{create|update|delete}.

Returns : confirmation et dossier technique mis à jour. Réponse inchangée si aucun champ n'était à écrire dans le mode demandé.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesID de la ressource dont le dossier technique est mis à jour.
modeNo'merge' (défaut) enrichit le DT sans rien écraser. 'replace' remplace intégralement chaque champ fourni.merge
titleNoTitre / poste actuel.
toolsNoOutils maîtrisés avec niveau (1-4).
skillsNoCompétences libres, séparées par virgule (ex: 'Python, AWS, GCP').
summaryNoRésumé / synthèse du parcours.
diplomasNoDiplômes (texte libre, ex: 'DUT Informatique - IUT Bordeaux (2016)').
trainingNoFormations / parcours académique.
languagesNoLangues parlées avec niveau.
experienceNoAnnées d'expérience.
activityAreasNoSecteurs d'activité.
expertiseAreasNoDomaines d'expertise (texte libre, ex: 'Banque').

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. First observedv2.1.0

TDQS

A4.9/5.0
Behavior5/5

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

Annotations already signal idempotent and non-destructive, and the description goes well beyond them by detailing merge vs replace semantics, per-field behavior, and the guarantee that omitted fields are never reset. It also discloses the response behavior, including unchanged output when nothing needed writing.

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 description is long but well-structured with clear sections, bullet lists, and mode explanations. There is minor redundancy between the opening sentence and the 'Quand' sentence, but every other part earns its place.

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 complex 12-parameter mutation with no output schema, the description covers purpose, usage context, sibling alternatives, merge/replace behavior, omitted-field semantics, and return behavior. Nothing essential for selecting or invoking the tool correctly 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?

Although the schema covers all parameters, the description adds substantial meaning beyond the schema: CSV handling for skills, key-based behavior for tools/languages, conditional filling for title/summary/training/experience, and field-by-field merge behavior. This directly helps an agent construct correct calls.

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: "Met à jour le dossier technique (DT) d'une ressource," and enumerates the exact fields covered (compétences, outils, langues, expertises, formations, diplômes, expérience). It also distinguishes itself from the reference-management siblings by explicitly stating that professional experiences are not handled here.

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?

The description includes a 'Quand' section stating when to use the tool and a 'Plutôt que' section routing professional-experience updates to boond_resources_reference_create/_update/_delete. It closes with an explicit instruction to use those sibling tools for références, leaving no ambiguity about tool selection.

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