Skip to main content
Glama
fauguste

boondmanager-mcp-server

by fauguste
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Détails d'un contrat

boond_contracts_get
Read-onlyIdempotent

Retrieve the complete contract record by its numeric ID to access attributes missing from list results. Use this after a search when you need the full entity details.

Instructions

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

Quand : après un boond_contracts_search, pour obtenir les attributs qui n'apparaissent pas dans le résumé de liste. Plutôt que : boond_contracts_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_contracts_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.7/5.0
Behavior4/5

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

Adds concrete behavioral details beyond the readOnlyHint annotation: unknown IDs return BoondManager's raw error, the tool does not accept a name, and the response shape (attributes + relations) is disclosed. The 'lecture seule' statement is consistent with annotations. Loses one point only because the read-only nature is already in the annotations and something like pagination/field-level detail is not covered.

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?

Front-loaded with the core action, then structured into clear 'Quand', 'Plutôt que', and 'Returns' segments. Compact, scannable, and every sentence adds information. No fluff.

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 tool, nothing is missing: what it returns ('JSON de l'entité... attributs + relations'), when to use it, when not to, error behavior for unknown IDs, and read-only status. The description fully covers the agent's decision and invocation needs.

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 fully describes the `id` parameter (required, numeric pattern) but the description adds meaningful usage semantics: the ID must come from boond_contracts_search, must not be guessed, and the tool rejects names. This goes beyond the schema's type/pattern constraints.

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?

States a specific verb ('Récupère la fiche complète') and resource ('un contrat'), explicitly distinguishing itself from boond_contracts_search (which is for finding contracts) and clarifying that it fetches the full record. The title and description align and the tool's purpose is unambiguous.

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?

Provides explicit when-to-use guidance ('Quand: après un boond_contracts_search'), when-not-to-use guidance ('Plutôt que: boond_contracts_search si l'ID n'est pas connu'), and a hard rule that the ID must come from search, never a guess. This fully equips the agent to choose between the get and search tools.

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