Skip to main content
Glama

search_events

Read-onlyIdempotent

Recherche unifiée d'événements de société (multi-SIREN), basée sur notre index ES.

Renvoie des ÉVÉNEMENTS individuels (pas des sociétés) : { date, type, siren, denomination, data }. Couvre 8 types : cession (cessions de fonds), procedure (procédures collectives), depot_comptes, augmentation_capital, marche_public, subvention, radiation, creation. Ce n'est PAS le fil de veille : pour les signaux récents des sociétés suivies (nouveau bilan, score crédit, dissolution...), utiliser get_news.

Couvre les événements BODACC (cessions, procédures collectives, radiations, créations) ainsi que les dépôts de comptes, augmentations de capital, marchés publics et subventions dérivés des scalaires silver.

RÈGLE : préciser au moins un filtre region / departement / ville / code_naf, OU un filtre d'événement (date_min, date_max, cedant_siren, cessionnaire_siren, prix_min/max, tribunal, procedure_type), sinon 400.

IMPORTANT : passer UN SEUL type quand la question porte sur un type précis. Les filtres de cadrage (existence de l'événement, fenêtre de dates) ne sont poussés dans la requête que dans ce cas ; avec plusieurs types ils s'excluraient mutuellement, et la recherche se rabat sur un tri général dont on ne lit que les premières pages : une question pointue y paraît vide.

Cas d'usage :

  • "Cessions de fonds > 1M en Île-de-France depuis 2024" → type="cession", region="Île-de-France", date_min="2024-01-01", prix_min=1000000

  • "Procédures collectives à Lyon" → type="procedure", ville="Lyon"

  • "Liquidations prononcées à Marseille en juillet 2026" → type="procedure", procedure_type="liquidation", ville="Marseille", date_min="2026-07-01", date_max="2026-07-31"

  • "Marchés publics récents dans le BTP" → type="marche_public", code_naf="4120A"

COÛT en crédits : 0,1 par événement retourné ; au quota : 1 unité par recherche.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "search_events"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeNoTypes d'événements (CSV) : cession, procedure, depot_comptes, augmentation_capital, marche_public, subvention, radiation, creation. Défaut : tous.
limitNoNombre d'événements (max 20 ; 1 000 par recherche)
villeNoVille du siège (CSV possible). Ex: "Marseille". Le bon filtre pour un ressort de tribunal : plus étroit que département.
cursorNoCurseur de pagination (au quota : abonnements)
regionNoRégion. Ex: "Île-de-France", "Bretagne"
code_nafNoCode NAF/APE. CSV possible, et un niveau supérieur couvre toutes ses sous-classes : division (49), groupe (49.4), section (H). Tous les codes d'une même question vont dans UN appel, jamais un appel par code.
date_maxNoDate max (YYYY-MM-DD)
date_minNoDate min (YYYY-MM-DD)
prix_maxNoPrix de vente max en euros (filtre cession)
prix_minNoPrix de vente min en euros (filtre cession)
tribunalNoTribunal (filtre procedure, recherche partielle)
departementNoCode département. Ex: "75", "69"
cedant_sirenNoSIREN du cédant (filtre cession)
procedure_typeNoType(s) de procédure (CSV) : liquidation, redressement, sauvegarde, conciliation
cessionnaire_sirenNoSIREN du cessionnaire (filtre cession)

Output Schema

NameRequiredDescriptionDefault
dataYes
paginationYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / cursor / description
      Previous value: -"Curseur de pagination (plan Pro uniquement)"New value: +"Curseur de pagination (au quota : abonnements)"
  2. Changed1 schema field changed
    • changedInput schema / properties / limit / description
      Previous value: -"Nombre d'événements (défaut 50, max 200)"New value: +"Nombre d'événements (max 20 ; 1 000 par recherche)"
  3. Changed8 schema fields changed
    • changedInput schema / properties / cedant_siren / description
      Previous value: -"SIREN du cedant (filtre cession)"New value: +"SIREN du cédant (filtre cession)"
    • changedInput schema / properties / code_naf / description
      Previous value: -"Code NAF/APE. CSV possible, et un niveau superieur couvre toutes ses sous-classes : division (49), groupe (49.4), section (H). Tous les codes d'une meme question vont dans UN appel, jamais un appel par code."New value: +"Code NAF/APE. CSV possible, et un niveau supérieur couvre toutes ses sous-classes : division (49), groupe (49.4), section (H). Tous les codes d'une même question vont dans UN appel, jamais un appel par code."
    • changedInput schema / properties / departement / description
      Previous value: -"Code departement. Ex: \"75\", \"69\""New value: +"Code département. Ex: \"75\", \"69\""
    • changedInput schema / properties / limit / description
      Previous value: -"Nombre d'evenements (defaut 50, max 200)"New value: +"Nombre d'événements (défaut 50, max 200)"
    • changedInput schema / properties / procedure_type / description
      Previous value: -"Type(s) de procedure (CSV) : liquidation, redressement, sauvegarde, conciliation"New value: +"Type(s) de procédure (CSV) : liquidation, redressement, sauvegarde, conciliation"
    • changedInput schema / properties / region / description
      Previous value: -"Region. Ex: \"Ile-de-France\", \"Bretagne\""New value: +"Région. Ex: \"Île-de-France\", \"Bretagne\""
    • changedInput schema / properties / type / description
      Previous value: -"Types d'evenements (CSV) : cession, procedure, depot_comptes, augmentation_capital, marche_public, subvention, radiation, creation. Defaut : tous."New value: +"Types d'événements (CSV) : cession, procedure, depot_comptes, augmentation_capital, marche_public, subvention, radiation, creation. Défaut : tous."
    • changedInput schema / properties / ville / description
      Previous value: -"Ville du siege (CSV possible). Ex: \"Marseille\". Le bon filtre pour un ressort de tribunal : plus etroit que departement."New value: +"Ville du siège (CSV possible). Ex: \"Marseille\". Le bon filtre pour un ressort de tribunal : plus étroit que département."
  4. Changed3 schema fields changed
    • addedInput schema / additionalProperties
      Added value: +false
    • removedInput schema / properties / llm_model
      Removed value: -{
      -  "description": "The exact model identifier you (the assistant) are running as, taken from your system prompt or environment (e.g. \"claude-opus-4-8\", \"gpt-5.2\"). Used for analytics only. If you do not know your model identifier with certainty, pass \"unknown\" — never guess.",
      -  "type": "string"
      -}
    • removedInput schema / required
      Removed value: -[
      -  "llm_model"
      -]
  5. Changed3 schema fields changed
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / llm_model
      Added value: +{
      +  "description": "The exact model identifier you (the assistant) are running as, taken from your system prompt or environment (e.g. \"claude-opus-4-8\", \"gpt-5.2\"). Used for analytics only. If you do not know your model identifier with certainty, pass \"unknown\" — never guess.",
      +  "type": "string"
      +}
    • addedInput schema / required
      Added value: +[
      +  "llm_model"
      +]
  6. Changed1 schema field changed
    • changedInput schema / properties / code_naf / description
      Previous value: -"Code NAF/APE (CSV possible)"New value: +"Code NAF/APE. CSV possible, et un niveau superieur couvre toutes ses sous-classes : division (49), groupe (49.4), section (H). Tous les codes d'une meme question vont dans UN appel, jamais un appel par code."
  7. Changed1 schema field changed
    • addedInput schema / properties / ville
      Added value: +{
      +  "description": "Ville du siege (CSV possible). Ex: \"Marseille\". Le bon filtre pour un ressort de tribunal : plus etroit que departement.",
      +  "type": "string"
      +}
  8. Changed1 schema field changed
    • removedInput schema / properties / ville
      Removed value: -{
      -  "description": "Ville du siege (CSV possible). Ex: \"Marseille\". Le bon filtre pour un ressort de tribunal : plus etroit que departement.",
      -  "type": "string"
      -}
  9. Changed1 schema field changed
    • addedInput schema / properties / ville
      Added value: +{
      +  "description": "Ville du siege (CSV possible). Ex: \"Marseille\". Le bon filtre pour un ressort de tribunal : plus etroit que departement.",
      +  "type": "string"
      +}
  10. Changed1 schema field changed
    • removedInput schema / properties / ville
      Removed value: -{
      -  "description": "Ville du siege (CSV possible). Ex: \"Marseille\". Le bon filtre pour un ressort de tribunal : plus etroit que departement.",
      -  "type": "string"
      -}
  11. Changed1 schema field changed
    • addedInput schema / properties / ville
      Added value: +{
      +  "description": "Ville du siege (CSV possible). Ex: \"Marseille\". Le bon filtre pour un ressort de tribunal : plus etroit que departement.",
      +  "type": "string"
      +}
  12. Changed1 schema field changed
    • removedInput schema / properties / ville
      Removed value: -{
      -  "description": "Ville du siege (CSV possible). Ex: \"Marseille\". Le bon filtre pour un ressort de tribunal : plus etroit que departement.",
      -  "type": "string"
      -}
  13. Changed1 schema field changed
    • addedInput schema / properties / ville
      Added value: +{
      +  "description": "Ville du siege (CSV possible). Ex: \"Marseille\". Le bon filtre pour un ressort de tribunal : plus etroit que departement.",
      +  "type": "string"
      +}
  14. Changed1 schema field changed
    • removedInput schema / properties / ville
      Removed value: -{
      -  "description": "Ville du siege (CSV possible). Ex: \"Marseille\". Le bon filtre pour un ressort de tribunal : plus etroit que departement.",
      -  "type": "string"
      -}
  15. Changed1 schema field changed
    • addedInput schema / properties / ville
      Added value: +{
      +  "description": "Ville du siege (CSV possible). Ex: \"Marseille\". Le bon filtre pour un ressort de tribunal : plus etroit que departement.",
      +  "type": "string"
      +}
  16. Changed1 schema field changed
    • removedInput schema / properties / ville
      Removed value: -{
      -  "description": "Ville du siege (CSV possible). Ex: \"Marseille\". Le bon filtre pour un ressort de tribunal : plus etroit que departement.",
      -  "type": "string"
      -}
  17. Changed1 schema field changed
    • addedInput schema / properties / ville
      Added value: +{
      +  "description": "Ville du siege (CSV possible). Ex: \"Marseille\". Le bon filtre pour un ressort de tribunal : plus etroit que departement.",
      +  "type": "string"
      +}
  18. Changed1 schema field changed
    • removedInput schema / properties / ville
      Removed value: -{
      -  "description": "Ville du siege (CSV possible). Ex: \"Marseille\". Le bon filtre pour un ressort de tribunal : plus etroit que departement.",
      -  "type": "string"
      -}
  19. Changed1 schema field changed
    • addedInput schema / properties / ville
      Added value: +{
      +  "description": "Ville du siege (CSV possible). Ex: \"Marseille\". Le bon filtre pour un ressort de tribunal : plus etroit que departement.",
      +  "type": "string"
      +}
  20. Changed3 schema fields changed
    • addedInput schema / additionalProperties
      Added value: +false
    • removedInput schema / properties / context
      Removed value: -{
      -  "description": "Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVER use first person ('I', 'we', 'you') - maintain third-person perspective. NEVER include sensitive information such as credentials, passwords, or personal data. Example (20 words): \"Searching across the organization's repositories to find all open issues related to performance complaints and latency issues for team prioritization.\"",
      -  "type": "string"
      -}
    • removedInput schema / required
      Removed value: -[
      -  "context"
      -]
  21. Changed3 schema fields changed
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / context
      Added value: +{
      +  "description": "Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVER use first person ('I', 'we', 'you') - maintain third-person perspective. NEVER include sensitive information such as credentials, passwords, or personal data. Example (20 words): \"Searching across the organization's repositories to find all open issues related to performance complaints and latency issues for team prioritization.\"",
      +  "type": "string"
      +}
    • addedInput schema / required
      Added value: +[
      +  "context"
      +]
  22. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Beyond the annotations (which already cover read-only, idempotent, non-destructive, closed-world), the description discloses credit cost (0.1 per returned event, 1 unit per search at quota), the failure mode of multiple types (mutually exclusive framing filters, fallback to a general sort where only the first pages are read, making narrow questions appear empty), and the 400 condition. These are exactly the operational traits an agent cannot infer from 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?

Well front-loaded: identity and return shape first, exclusions and rules next, then use cases, then cost. Slightly long, with the eight event types enumerated twice (prose list, then the BODACC/silver source paragraph), which is mild redundancy rather than wasted space.

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?

For a 15-parameter, zero-required search tool with an output schema, the description covers everything an agent needs: what is returned, which filters are mandatory, the single-type pitfall, error behavior, and cost. Return-value detail is appropriately left to the output schema rather than duplicated.

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 100% schema coverage the baseline is 3; the description adds real cross-parameter semantics the schema cannot express, notably that framing filters are only pushed when a single type is supplied, and that the geo/event filter pair is required. It also grounds parameters in concrete examples (prix_min=1000000 for '>1M', procedure_type='liquidation' with a date window), though some CSV guidance overlaps what the schema already states.

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 and resource ('Recherche unifiée d'événements de société (multi-SIREN)'), enumerates the eight covered event types, and explicitly clarifies it returns individual EVENTS, not companies, with the returned field shape listed. It also names the sibling it is not ('Ce n'est PAS le fil de veille ... utiliser get_news'), so an agent can route correctly without opening a 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?

Gives when-to-use, an explicit exclusion with a named alternative (get_news for recent signals on watched companies), and a hard precondition: at least one region/departement/ville/code_naf or event filter, otherwise a 400. It further advises passing a single type when the question targets one type, and supplies four worked question-to-parameters mappings.

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.

Resources