Skip to main content
Glama
fauguste

boondmanager-mcp-server

by fauguste

Supprimer un(e) société

boond_companies_delete
Destructive

Delete a company permanently in BoondManager. Irreversible action for removing company records.

Instructions

Supprime un(e) société de BoondManager. ⚠️ Action irréversible.

Args:

  • id (string): Identifiant de l'entité à supprimer

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesIdentifiant unique de l'entité BoondManager
Behavior3/5

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

The description adds 'Action irréversible' which aligns with the destructiveHint annotation, but provides no additional behavioral context beyond what annotations already supply. It does not contradict 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 extremely concise—two sentences—with essential information front-loaded: the action, the warning, and the parameter. No unnecessary words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's simplicity (one parameter, annotated destructive), the description is adequate but not complete. It does not mention return values (no output schema) or side effects beyond irreversibility. For context completeness, it could describe what happens after deletion (e.g., success response).

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 schema already fully describes the 'id' parameter with 100% coverage. The description's list of args merely restates this information, adding minimal semantic value. Baseline 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 clearly states that the tool deletes a company (société) in BoondManager with the verb 'Supprime' and resource 'société'. It distinguishes itself from sibling tools like boond_companies_create and boond_companies_update. The warning 'Action irréversible' further clarifies the action.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies use when you want to delete a company, but it lacks explicit guidance on when to use this tool versus other deletion tools or when not to use it (e.g., if there are dependencies). No alternatives or prerequisites are mentioned.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/fauguste/boondmanager-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server