Skip to main content
Glama
fauguste

boondmanager-mcp-server

by fauguste
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Productivité d'un projet

boond_projects_productivity
Read-onlyIdempotent

Retrieve a project's productivity data, including time spent and days consumed, by its unique ID. Use this tool to load only the productivity section without fetching the full project record.

Instructions

Récupère les données de productivité (temps passé, jours consommés) d'un(e) projet, par son ID.

Quand : pour ne charger que cette section, sans le reste de la fiche. Plutôt que : boond_projects_get pour la fiche de base, ou boond_projects_search si l'ID est inconnu.

Returns : Consommé du projet — du réalisé, contrairement à boond_projects_simulation. 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.5/5.0
Behavior4/5

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

The annotations already establish read-only, idempotent, non-destructive behavior, so the description does not need to restate those. It adds useful behavioral context by clarifying that the returned values are 'Consommé du projet' (actuals) rather than simulated data, which is a meaningful semantic distinction beyond the structured metadata.

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 compact and organized with clear keywords ('Quand', 'Plutôt que', 'Returns'). Every sentence contributes actionable guidance — what it returns, when to use it, which sibling to prefer.

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?

The tool has one parameter, is fully covered by the schema, and has meaningful annotations. The description provides the purpose, the usage conditions, and the nature of the returned data (`temps passé`, `jours consommés`, actuals vs. simulation), making it complete enough for an agent to call correctly without an output schema.

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?

The input schema documents the single `id` parameter fully with type, pattern, and description. The description's 'par son ID' adds no new parameter meaning; it merely restates what the schema already says. With 100% schema description coverage, a baseline score of 3 is appropriate.

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 action ('Récupère les données de productivité'), a precise resource ('d'un projet'), and the fields involved ('temps passé, jours consommés'). It also differentiates the tool from siblings by stating it loads only the productivity section, unlike `boond_projects_get` or `boond_projects_search`.

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 explicitly says when to use this tool ('pour ne charger que cette section, sans le reste de la fiche') and names alternatives with the exact condition for choosing them: `boond_projects_get` for the base record, `boond_projects_search` when the ID is unknown. It also distinguishes from `boond_projects_simulation`, leaving little ambiguity.

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