Skip to main content
Glama

Find which French legal notices a company must publish

which_legal_notice
Read-onlyIdempotent

Use this when a French company or its adviser describes a corporate event (creation, registered office transfer within or outside the department, change of manager or president, name, corporate purpose, share capital, legal form, duration, dissolution, liquidation closure, sale of a business…) and needs to know which legal notices are mandatory, how many, in which department, on what legal basis and at what price. The answer comes from a fixed table of rules; when it needs one more fact, it returns a question instead of a guess. Do not use for court-ordered insolvency notices or for legal advice on whether to take the decision.

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": {
      "situations": "<situations>"
    },
    "name": "which_legal_notice"
  }
}

Input Schema

NameRequiredDescriptionDefault
legalFormNoCurrent legal form (required for company_creation and legal_form_change).
departmentNoDepartment of the registered office (before a transfer).
situationsYesEvents decided together, e.g. ["seat_transfer", "officer_change"].
newLegalFormNoLegal form after a legal_form_change.
newDepartmentNoDepartment of the new registered office (seat_transfer).
sameCommercialCourtNoseat_transfer within one department that has several commercial courts: does the new office depend on the same court?
soleShareholderIsCompanyNodissolution_without_liquidation: is the sole shareholder a company?

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/closed-world, but the description adds genuinely new behavior: the answer comes from a fixed rule table and, when a required fact is missing, the tool returns a clarifying question rather than guessing. That is exactly the kind of non-obvious interaction pattern an agent needs and cannot get from the annotations.

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?

Front-loaded with the trigger condition, then the output contract, then the exclusions — a good order. The long parenthetical of event types largely duplicates the situations enum and costs a line without adding routing value.

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 7-parameter, rule-driven tool with no output schema, the description conveys what the answer contains and that a question may come back instead. It stops short of explaining how to answer that follow-up question (which parameter to fill), a minor gap given the schema documents each conditional field.

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%, including the legalForm/department conditionality and enum lists, so the schema carries parameter meaning. The description's prose event list roughly mirrors the situations enum but adds no formatting or dependency detail beyond it, so baseline 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+resource (determine which French legal notices are mandatory) and enumerates the exact outputs of the decision: how many, which department, legal basis, price. This clearly separates it from prepare_legal_notice and get_legal_notice_price, which act on a single notice rather than resolving which notices apply.

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?

Opens with an explicit trigger ('Use this when a French company or its adviser describes a corporate event…') and adds two exclusions (court-ordered insolvency notices, legal advice on whether to decide). It does not name the sibling tools to use in those excluded cases, so the alternative routing is left implicit.

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.