Skip to main content
Glama
silamir

boondmanager-mcp-server

by silamir
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Détails d'un(e) paiement

boond_payments_get
Read-onlyIdempotent

Retrieve a complete payment record by numeric ID to access attributes missing from list summaries. Use after a payment search to get full entity details.

Instructions

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

Quand : après un boond_payments_search, pour obtenir les attributs qui n'apparaissent pas dans le résumé de liste. Plutôt que : boond_payments_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_payments_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?

Annotations already declare readOnlyHint, destructiveHint, and idempotentHint, so the description need not repeat those. It adds useful context: that unknown IDs propagate the BoondManager error as-is, that the return is the full JSON entity (attributes + relations), and that the operation is read-only. This goes beyond the annotations.

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, front-loaded with the core purpose, then structured usage guidance (Quand, Plutôt que), a warning bullet, and a returns note. Every sentence adds value with no redundancy, achieving high information density.

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 simple get-by-id tool with one parameter, annotations covering safety, and no output schema, the description is complete. It covers when to use, how to obtain the ID, error behavior, and return format. Nothing essential 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 provides 100% coverage for the single 'id' parameter with a description. The description adds critical semantic guidance: the ID must come from boond_payments_search, never be guessed, and that the tool only accepts numeric IDs. This enriches the schema's basic definition.

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 clearly states the tool retrieves the complete record of a payment by its numeric ID, and explicitly contrasts with the search tool that returns list summaries. It names the specific resource and operation, distinguishing it from siblings like boond_payments_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?

Explicit guidance on when to use (after a search to get full attributes) and when not to use (if ID is unknown, use search instead). It also warns that the ID must come from search, not guesswork, providing clear alternatives and constraints.

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