delete_property_workSupprime un poste de travaux immobiliers par son identifiant. Les documents justificatifs associés sont également supprimés. Cette action est irréversible.
| Name | Required | Description | Default |
|---|---|---|---|
| work_id | Yes |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The annotations already declare destructiveHint=true, but the description adds critical beyond-annotation context: 'Les documents justificatifs associés sont également supprimés' (associated supporting documents are also deleted) and 'Cette action est irréversible' (this action is irreversible). This discloses cascading side effects and permanence.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Three short, front-loaded sentences each add essential information: the action, the cascading deletion, and irreversibility. No redundancy, perfectly sized.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a single-parameter delete operation with no output schema, the description covers the action, side effects, and irreversibility, providing sufficient context for an agent to invoke it correctly.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The input schema only lists work_id as an integer. The description clarifies that work_id is the identifier of the property work, giving semantic meaning to the parameter. With 0% schema description coverage, this is helpful though not exhaustive.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the action with a specific verb and resource: 'Supprime un poste de travaux immobiliers par son identifiant' (deletes a property work item by its identifier). It also distinguishes from sibling delete tools by explicitly mentioning 'travaux immobiliers' (property works).
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description gives clear context that this tool is for deleting property works and warns that associated documents are also deleted. It does not explicitly name alternative tools or provide when-not-to-use guidance, but the context is sufficient for basic selection.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
The set contains two almost identical comparison tools: compare_micro_bic and get_simulation both compute micro-BIC vs réel and recommend the best regime. This creates a direct selection conflict. Other tools are mostly distinct, but this overlap is significant.
Tool names follow a verb_noun pattern consistently, with list_properties, create_income, delete_expense, etc. Minor deviations exist such as compare_micro_bic (no standard noun) and the plural/singular mismatch between delete_document and export_documents, but these are easily understood.
With 44 tools, the surface is very large for an MCP server. While the LMNP domain is broad, the number exceeds the typical range and will be hard for agents to navigate efficiently. Some functions could be consolidated (e.g., get_simulation absorbs compare_micro_bic).
The set covers CRUD for properties, incomes, expenses, furniture, and works, plus documents and fiscal computations. However, there is no create/update/delete for loans (only compute and get), no delete_property, and no update for property components. These gaps could block common workflows.