Skip to main content
Glama

Montant encaissé d'un contact

ficiel_set_lead_deal_amount
DestructiveIdempotent

Pose, corrige ou retire (null) le montant réellement encaissé avec un contact, en centimes (entier de 0 à 100 000 000, soit 1 000 000 €). C'est le chiffre qui alimente le cash signé. Ne change ni l'étape (ficiel_set_stage, qui date la signature au passage en client) ni rien d'autre. Rend l'ancien et le nouveau montant. Mêmes portes que ficiel_get_cash (drapeau Cash, organisation abonnée). Portée « write » requise.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "lead_id": "<lead_id>",
      "deal_amount_cents": "<deal_amount_cents>"
    },
    "name": "ficiel_set_lead_deal_amount"
  }
}

Input Schema

NameRequiredDescriptionDefault
lead_idYesIdentifiant du contact (lead_id).
deal_amount_centsYesMontant en centimes (ex. 117000 pour 1 170 €), ou null pour le retirer.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already flag write (readOnlyHint=false), idempotent and destructive; the description adds real substance on top: null semantics for removal, the returned old/new values, the exact gating (Cash flag, subscribed organisation) and the required write scope. That is meaningful behavioral context beyond the structured fields.

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?

Dense but front-loaded: the action and the null-removal case come first, followed by scope boundaries, return values and gates. Every clause carries information; the parenthetical € conversion slightly duplicates the schema but is cheap.

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?

With no output schema, the description compensates by stating the return ('Rend l'ancien et le nouveau montant'), and it covers mutation semantics, gating and scope. For a two-parameter write tool, nothing an agent needs to call it correctly is missing.

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?

Schema description coverage is 100% and both parameters are already documented with units, bounds and the null case in the schema itself. The description restates the centimes range and the € equivalent but adds no syntax or format detail the schema lacks, so the baseline of 3 applies.

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 triplet (pose/corrige/retire) on a precise resource (le montant réellement encaissé d'un contact), including the null-removal case. It explicitly distinguishes itself from ficiel_set_stage ('Ne change ni l'étape ... ni rien d'autre') and ties the value to the 'cash signé' concept, so an agent can separate it from stage and average-deal tools without opening schemas.

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

Usage Guidelines4/5

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

Gives clear context ('le chiffre qui alimente le cash signé'), an explicit exclusion (does not change stage), and the gating conditions ('Mêmes portes que ficiel_get_cash', 'Portée « write » requise'). It does not explicitly contrast with the closest sibling ficiel_set_average_deal, so it stops short of full when/when-not guidance.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.