Skip to main content
Glama
silamir

boondmanager-mcp-server

by silamir
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Mettre à jour le dossier technique d'une ressource

boond_resources_technical_data_update
Idempotent

Update a resource's technical data (skills, tools, languages, diplomas) using merge or replace mode, adding or replacing only specified fields while leaving others untouched.

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. Changed2 schema fields changedv2.17.0
    • removedInput schema / properties / id / minLength
      Removed value: -1
    • addedInput schema / properties / id / pattern
      Added value: +"^\\d+$"
  2. Changed1 schema field changedv2.12.2
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
  3. First observedv2.1.0

TDQS

A5/5.0
Behavior5/5

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

The description goes well beyond the annotations by explaining the default merge mode, per-field merge behavior, the replace mode, and that omitted fields are never reset to empty. It also states what the API returns and notes that the response is unchanged if nothing was written, making the update semantics highly transparent.

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 structured with clear headers and bullets, front-loads the core purpose, and then adds usage guidance, mode semantics, exclusions, and return behavior. Each section earns its place and no meaningful information is repeated or wasted.

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 tool with 12 parameters, two behavioral modes, sibling overlap, and no output schema, the description covers everything needed: purpose, when to use, alternatives, field-level merge/replace semantics, safety caveats, and return value. No critical operational aspect 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?

Even though schema description coverage is 100%, the description adds crucial behavioral meaning to parameters: it explains how skills, tools, languages, expertiseAreas, activityAreas, diplomas, title, summary, training, and experience behave differently in merge vs replace mode. This is exactly the kind of semantic depth an agent needs beyond the schema.

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 clear action verb and object: 'Met à jour le dossier technique (DT) d'une ressource', and immediately lists the affected fields (compétences, outils, langues, expertises, formations, diplômes, expérience). It also explicitly excludes professional experiences and routes those to sibling tools, distinguishing itself from boond_resources_reference_create/update/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?

The description has a dedicated 'Quand' section stating when to use the tool and a 'Plutôt que' section naming the alternative tools for professional experiences. It also explains why the alternatives are preferable in that specific case, giving an agent actionable routing 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