Skip to main content
Glama

Change a legal notice draft prepared on legalone.fr

update_legal_notice_draft
Idempotent

Use this when the user wants to add or correct a fact in a draft that prepare_legal_notice created in this conversation (a forgotten duration, another date, a misspelt name): send its draftId and editToken, the formality and only the fields to change; the others stay as they are. Send decisionDate and effectiveDate together, and each officer with its type and, when its role can hold several people, its index (1 for the first of that role in the draft). Returns the new notice text and what the form still requires; the link already given keeps opening the draft, until the same expiry. Do not use for a draft the user has already saved on legalone.fr (it is then theirs, and is changed on the form), nor to start another notice: use prepare_legal_notice. Same privacy rules as prepare_legal_notice.

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": {
      "draftId": "<draftId>",
      "editToken": "<editToken>",
      "formality": "<formality>"
    },
    "name": "update_legal_notice_draft"
  }
}

Input Schema

NameRequiredDescriptionDefault
sirenNoSIREN of the existing company (9 digits, spaces allowed). Required for a change; none for a creation.
acronymNoCreation: acronym (optional).
capitalNoCreation: share capital in euros (fixed capital).
draftIdYesdraftId returned by prepare_legal_notice.
newNameNoNew company name.
purposeNoCreation: corporate purpose, as written in the articles.
deedDateNoCreation: date the articles of association were signed (YYYY-MM-DD).
deedTypeNoCreation: form of the articles of association.
officersNoCreation drafts only: the officers to change, each with its role, its type and its index. Roles by formality: eurl/sarl/sc/sci/sccv/scm/scpi/scp/seleurl/selarl: manager; sasu: president, chief_executive, deputy_chief_executive, other_chief_executive, auditor, substitute_auditor; sas: president, chief_executive, deputy_chief_executive, director, other_chief_executive, auditor, substitute_auditor; snc: manager, partner, co_manager, auditor, substitute_auditor; sa: president, chief_executive, deputy_chief_executive, director, management_board_member, auditor, substitute_auditor; selas/selasu: president, chief_executive, deputy_chief_executive, auditor, substitute_auditor; selafa: president, chief_executive, deputy_chief_executive, director, auditor, substitute_auditor.
seatCityNoCreation: registered office, city.
editTokenYeseditToken returned by prepare_legal_notice, for this draft only.
formalityYesFormality of the draft, as sent to prepare_legal_notice (it cannot change).
seatCourtNoCreation: commercial court (greffe) of registration, e.g. Bobigny; deduced when the department has one court.
tradeNameNoCreation: trade name (optional).
departmentNoPublication department, used only when it cannot be read from the registered office (the notice is published where the office is).
newAcronymNoNew acronym (optional).
newCapitalNoShare capital after the operation, in euros.
newPurposeNoCorporate purpose as written in the decision.
notaryCityNoCreation by notarial deed: city where the notary practises.
notaryNameNoCreation by notarial deed: name of the notary.
professionNoCreation of a société d'exercice libéral (seleurl, selarl, selas, selasu, selafa), optional: profession practised, as in the articles, e.g. avocat. The notice prints it when given.
seatStreetNoCreation: registered office, number and street.
companyNameNoCreation: name of the company, as in the articles.
newSeatCityNoNew registered office: city.
officerRoleNo
decisionBodyNoBody that took the decision: a general meeting; the partners or shareholders deciding collectively (meeting not specified or written consultation) or unanimously (act signed by all); the sole partner; the manager or the management (several managers); the president or the managing director (SAS, SA); the board of directors, the management board (directoire) or the supervisory board (SA, SCA). other: any other body, named in decisionBodyOther.
decisionDateNoDate of the meeting or decision (YYYY-MM-DD).
newSeatCourtNoCommercial court (greffe) of the new registered office, e.g. Nanterre; deduced when the department has one court.
capitalChangeNo
effectiveDateNoDate the decision takes effect (YYYY-MM-DD).
newSeatStreetNoNew registered office: number and street.
officerChangeNoappointment: a new officer without departure; replacement: one leaves, one arrives; departure: one leaves without replacement.
purposeChangeNo
departureCauseNo
initialCapitalNoCreation with a variable capital: initial capital in euros.
maximumCapitalNoCreation with a variable capital: maximum capital in euros.
minimumCapitalNoCreation with a variable capital: minimum capital in euros.
seatComplementNoCreation: registered office, building or floor (optional).
seatPostalCodeNoCreation: registered office, 5-digit postcode.
liquidationSeatNoWhere the liquidation is based.
incomingCivilityNo
incomingLastNameNo
newDurationYearsNoNew company duration in years.
decisionBodyOtherNoOnly when decisionBody is other (sent alone, it implies other): the body as the notice prints it after « Par décision », in French, starting with du, de la, de l' or des, e.g. « du comité de direction ».
departingCivilityNo
departingLastNameNo
incomingFirstNameNo
newSeatComplementNoNew registered office: building, floor (optional).
newSeatPostalCodeNoNew registered office: 5-digit postcode.
contributionNatureNo
departingFirstNameNo
liquidatorCivilityNo
liquidatorLastNameNo
representativeRoleNoRole of the legal representative named in the arrival notice.
liquidatorFirstNameNo
shareTransferClauseNoCreation of a share company (SAS, SA…): clause on the transfer of shares, as in the articles.
companyDurationYearsNoCompany duration in years, as in the articles of association. Required for a creation, an extension of duration and a transfer to another registry (the notice prints it), otherwise optional: send it whenever the user knows it; when required and absent, it comes back in missing.
meetingAdmissionClauseNoCreation of a share company (SAS, SA…): clause on admission to meetings and voting rights, as in the articles.
representativeCivilityNo
representativeLastNameNo
representativeFirstNameNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / officers / description
      Previous value: -"Creation only: the officers and auditors the notice names, with a person's home address as the notice publishes it. Roles by formality: eurl/sarl/sc/sci/sccv/scm/scpi/scp/seleurl/selarl: manager; sasu: president, chief_executive, deputy_chief_executive, other_chief_executive, auditor, substitute_auditor; sas: president, chief_executive, deputy_chief_executive, director, other_chief_executive, auditor, substitute_auditor; snc: manager, partner, co_manager, auditor, substitute_auditor; sa: president, chief_executive, deputy_chief_executive, director, management_board_member, auditor, substitute_auditor; selas/selasu: president, chief_executive, deputy_chief_executive, auditor, substitute_auditor; selafa: president, chief_executive, deputy_chief_executive, director, auditor, substitute_auditor."New value: +"Creation drafts only: the officers to change, each with its role, its type and its index. Roles by formality: eurl/sarl/sc/sci/sccv/scm/scpi/scp/seleurl/selarl: manager; sasu: president, chief_executive, deputy_chief_executive, other_chief_executive, auditor, substitute_auditor; sas: president, chief_executive, deputy_chief_executive, director, other_chief_executive, auditor, substitute_auditor; snc: manager, partner, co_manager, auditor, substitute_auditor; sa: president, chief_executive, deputy_chief_executive, director, management_board_member, auditor, substitute_auditor; selas/selasu: president, chief_executive, deputy_chief_executive, auditor, substitute_auditor; selafa: president, chief_executive, deputy_chief_executive, director, auditor, substitute_auditor."
    • addedInput schema / properties / officers / items / properties / index
      Added value: +{
      +  "description": "Which officer of this role the entry changes, in the order of the draft (1 for the first; for chief_executive, count all the directeurs généraux). Required when the role can hold several people; the other officers stay as they are.",
      +  "maximum": 10,
      +  "minimum": 1,
      +  "type": "integer"
      +}
  2. Changed2 schema fields changed
    • changedInput schema / properties / officers / description
      Previous value: -"Creation only: the officers and auditors the notice names, with a person's home address as the notice publishes it. Roles by formality: eurl/sarl/sc/sci/sccv/scm/scpi/scp/seleurl/selarl: manager; sasu/selas/selasu: president, chief_executive, deputy_chief_executive, auditor, substitute_auditor; sas/selafa: president, chief_executive, deputy_chief_executive, director, auditor, substitute_auditor; snc: manager, partner, co_manager, auditor, substitute_auditor; sa: president, chief_executive, deputy_chief_executive, director, management_board_member, auditor, substitute_auditor."New value: +"Creation only: the officers and auditors the notice names, with a person's home address as the notice publishes it. Roles by formality: eurl/sarl/sc/sci/sccv/scm/scpi/scp/seleurl/selarl: manager; sasu: president, chief_executive, deputy_chief_executive, other_chief_executive, auditor, substitute_auditor; sas: president, chief_executive, deputy_chief_executive, director, other_chief_executive, auditor, substitute_auditor; snc: manager, partner, co_manager, auditor, substitute_auditor; sa: president, chief_executive, deputy_chief_executive, director, management_board_member, auditor, substitute_auditor; selas/selasu: president, chief_executive, deputy_chief_executive, auditor, substitute_auditor; selafa: president, chief_executive, deputy_chief_executive, director, auditor, substitute_auditor."
    • changedInput schema / properties / officers / items / properties / role / enum
      Previous value: -[
      -  "manager",
      -  "president",
      -  "chief_executive",
      -  "deputy_chief_executive",
      -  "director",
      -  "management_board_member",
      -  "partner",
      -  "co_manager",
      -  "auditor",
      -  "substitute_auditor"
      -]New value: +[
      +  "manager",
      +  "president",
      +  "chief_executive",
      +  "other_chief_executive",
      +  "deputy_chief_executive",
      +  "director",
      +  "management_board_member",
      +  "partner",
      +  "co_manager",
      +  "auditor",
      +  "substitute_auditor"
      +]
  3. Changed1 schema field changed
    • addedInput schema / properties / profession
      Added value: +{
      +  "description": "Creation of a société d'exercice libéral (seleurl, selarl, selas, selasu, selafa), optional: profession practised, as in the articles, e.g. avocat. The notice prints it when given.",
      +  "maxLength": 200,
      +  "minLength": 1,
      +  "type": "string"
      +}
  4. Changed3 schema fields changed
    • changedInput schema / properties / decisionBody / description
      Previous value: -"Body that took the decision."New value: +"Body that took the decision: a general meeting; the partners or shareholders deciding collectively (meeting not specified or written consultation) or unanimously (act signed by all); the sole partner; the manager or the management (several managers); the president or the managing director (SAS, SA); the board of directors, the management board (directoire) or the supervisory board (SA, SCA). other: any other body, named in decisionBodyOther."
    • changedInput schema / properties / decisionBody / enum
      Previous value: -[
      -  "ordinary_general_meeting",
      -  "extraordinary_general_meeting",
      -  "combined_general_meeting",
      -  "manager",
      -  "president",
      -  "board_of_directors",
      -  "sole_shareholder",
      -  "shareholders_collective_decision"
      -]New value: +[
      +  "ordinary_general_meeting",
      +  "extraordinary_general_meeting",
      +  "combined_general_meeting",
      +  "shareholders_collective_decision",
      +  "shareholders_unanimous_decision",
      +  "sole_shareholder",
      +  "manager",
      +  "management",
      +  "president",
      +  "chief_executive",
      +  "board_of_directors",
      +  "management_board",
      +  "supervisory_board",
      +  "other"
      +]
    • addedInput schema / properties / decisionBodyOther
      Added value: +{
      +  "description": "Only when decisionBody is other (sent alone, it implies other): the body as the notice prints it after « Par décision », in French, starting with du, de la, de l' or des, e.g. « du comité de direction ».",
      +  "maxLength": 200,
      +  "minLength": 1,
      +  "type": "string"
      +}
  5. Added

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=true and openWorldHint=true, and the description backs that up with genuine patch semantics ('only the fields to change; the others stay as they are'), which explains why the call is idempotent. It also discloses the returns (new notice text plus what the form still requires) and that the existing link keeps working until the same expiry — context annotations cannot express. It stops short of stating any rate limits, auth or failure modes, so 4 rather than 5.

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?

One dense paragraph, but it is front-loaded with the trigger and the payload before moving to returns, then exclusions. Every clause carries information; the only soft spot is the trailing 'Same privacy rules as prepare_legal_notice', which points at context rather than stating it.

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

Completeness4/5

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

For a 61-parameter, no-output-schema mutation tool this covers the essentials: what mode it operates in, what must be sent, what stays untouched, what comes back, and what happens to the shared link. It leaves the creation-only parameter family unexplained, but those fields are explicitly not applicable to an edit, so the omission is defensible.

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?

With 61 parameters at 72% schema coverage, the description adds meaning the schema cannot: draftId, editToken and formality are the required trio, in edit mode only the changed fields should be sent, decisionDate and effectiveDate must be sent together, and each officer needs its type plus an index when the role can hold several people (1 = first of that role). That is real cross-field and conditional guidance beyond per-parameter descriptions.

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 gives a specific verb pair (add or correct a fact) and a precise resource (a draft created by prepare_legal_notice in this conversation), and immediately names the sibling it is not (prepare_legal_notice) so the agent can route without opening either schema.

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?

It states explicit triggers (forgotten duration, wrong date, misspelt name), explicit exclusions (a draft the user already saved on legalone.fr, which is edited on the form; starting another notice), and the alternative to use instead. It also gives the prerequisite that draftId and editToken must come from prepare_legal_notice in the same conversation.

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.