Skip to main content
Glama
digitalfactorysn

MCP Dolibarr Expert

add_intervention_line

Add a time entry line to an existing intervention sheet, specifying duration, description, and optional billing details like unit price and tax rate.

Instructions

Ajouter une ligne de temps à une fiche d'intervention

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesID de la fiche d'intervention
qtyNoQuantité (heures)
dateNoDate ISO 8601
descYesDescription de la prestation
dureeYesDurée en secondes (ex: 3600 = 1h)
tva_txNoTaux TVA %
subpriceNoPrix unitaire HT/heure
fk_productNo
Behavior2/5

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

With no annotations, the description carries the full burden of disclosing behavioral traits. It merely says 'Ajouter' without mentioning that it mutates the intervention, whether it requires an existing intervention, or what the response looks like. This is a significant gap for a mutation tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, front-loaded sentence with no wasted words. It is concise, though it could have included a short clause with usage guidance without becoming verbose.

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

Completeness1/5

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

For an 8-parameter mutation tool with no output schema and no annotations, this description is drastically under-specified. It lacks any behavioral details, prerequisites, return information, or relation to the intervention lifecycle, making it inadequate for an agent to invoke correctly.

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 describes 8 parameters with 88% coverage, including units and examples, so the description isn't required to add parameter details. The phrase 'ligne de temps' hints at the temporal nature (duree, qty), but no extra meaning is added beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action ('Ajouter') and the resource ('une ligne de temps à une fiche d'intervention'), distinguishing it from other line-add tools by targeting interventions. However, it doesn't elaborate on what a 'ligne de temps' specifically entails beyond the name.

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

Usage Guidelines2/5

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

No guidance is given on when to use this tool, what prerequisites exist (e.g., the intervention must already exist), or any alternatives. The description only states the action, leaving the agent to infer context from the tool name and schema.

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/digitalfactorysn/mcp-dolibarr'

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