Skip to main content
Glama

HelpMyAgent

by io.github.helpmyagent
OverviewDiscussionsAdmin

French Company Events

company_fr_events

Returns the latest normalized public BODACC events for a French company from a SIREN or SIRET. Use when: You need recent normalized BODACC events for a French company, such as filings, modifications, collective proceedings or deregistrations. You need an event timeline filtered from an optional publication date. Avoid when: You need an interpreted legal-risk level rather than raw normalized events; use company/fr/risk. You only need current administrative profile fields; use company/fr/profile. Limitations: The result reflects BODACC records available through the public dataset and the requested limit/date filter. Normalized events are factual source records and do not constitute legal advice or a risk score. Price: 0.010 USD per call via x402. Paid-call behavior: source records are not modified, but a successful invocation can consume the advertised x402 payment; the payment-required challenge is free, and repeating the tool after a completed paid invocation may require a new payment. Accepted x402 networks: eip155:8453, xrpl:0.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum number of normalized BODACC events to return
sinceNoMinimum included BODACC publication date in YYYY-MM-DD format
identifierYes9-digit SIREN or 14-digit SIRET

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesPublicly available company, person, buyer or record name for this result.
sirenYesNormalized 9-digit French SIREN when available.
eventsYesNormalized public events returned by the endpoint.
existsYesWhether the requested company or public record was found in the checked source.
truncatedYesWhether additional matching records existed beyond the returned result limit.
identifierYesIdentifier supplied for the request, echoed in normalized form when applicable.
total_countYesTotal number of matching records reported by the source or endpoint.
latest_eventYesStructured value returned for “latest event” as defined by this API contract.
returned_countYesNumber of records included in this response.
identifier_typeYesNormalized identifier type, such as SIREN or SIRET when applicable. (allowed values: siren, siret).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed24 schema fields changed
    • addedInput schema / description
      Added value: +"Structured input parameters for the company/fr/events API."
    • addedOutput schema / description
      Added value: +"Structured result returned by the company/fr/events API."
    • addedOutput schema / properties / events / description
      Added value: +"Normalized public events returned by the endpoint."
    • addedOutput schema / properties / events / items / properties / city / description
      Added value: +"Structured value returned for “city” as defined by this API contract."
    • addedOutput schema / properties / events / items / properties / department / description
      Added value: +"Structured value returned for “department” as defined by this API contract."
    • addedOutput schema / properties / events / items / properties / event_date / description
      Added value: +"Structured value returned for “event date” as defined by this API contract."
    • addedOutput schema / properties / events / items / properties / family / description
      Added value: +"Structured value returned for “family” as defined by this API contract."
    • addedOutput schema / properties / events / items / properties / family_code / description
      Added value: +"Structured value returned for “family code” as defined by this API contract."
    • addedOutput schema / properties / events / items / properties / id / description
      Added value: +"Structured value returned for “id” as defined by this API contract."
    • addedOutput schema / properties / events / items / properties / notice_type / description
      Added value: +"Structured value returned for “notice type” as defined by this API contract."
    • addedOutput schema / properties / events / items / properties / publication_date / description
      Added value: +"Structured value returned for “publication date” as defined by this API contract."
    • addedOutput schema / properties / events / items / properties / title / description
      Added value: +"Structured value returned for “title” as defined by this API contract."
    • addedOutput schema / properties / events / items / properties / tribunal / description
      Added value: +"Structured value returned for “tribunal” as defined by this API contract."
    • addedOutput schema / properties / events / items / properties / type / description
      Added value: +"Structured value returned for “type” as defined by this API contract. (allowed values: collective_procedure, radiation, accounts_filing, act, modification, other)."
    • addedOutput schema / properties / events / items / properties / url / description
      Added value: +"Structured value returned for “url” as defined by this API contract."
    • addedOutput schema / properties / exists / description
      Added value: +"Whether the requested company or public record was found in the checked source."
    • addedOutput schema / properties / identifier / description
      Added value: +"Identifier supplied for the request, echoed in normalized form when applicable."
    • addedOutput schema / properties / identifier_type / description
      Added value: +"Normalized identifier type, such as SIREN or SIRET when applicable. (allowed values: siren, siret)."
    • addedOutput schema / properties / latest_event / description
      Added value: +"Structured value returned for “latest event” as defined by this API contract."
    • addedOutput schema / properties / name / description
      Added value: +"Publicly available company, person, buyer or record name for this result."
    • addedOutput schema / properties / returned_count / description
      Added value: +"Number of records included in this response."
    • addedOutput schema / properties / siren / description
      Added value: +"Normalized 9-digit French SIREN when available."
    • addedOutput schema / properties / total_count / description
      Added value: +"Total number of matching records reported by the source or endpoint."
    • addedOutput schema / properties / truncated / description
      Added value: +"Whether additional matching records existed beyond the returned result limit."
  2. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Even though annotations only signal non-read-only/non-idempotent behavior, the description explicitly states source records are not modified, that paid invocation consumes x402 payment, that the challenge is free, and that repeat calls may require new payment. It also discloses factual-source limitations and no legal-advice scope.

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?

Structured with bolded Use when/Avoid when/Limitations/Price sections makes the long content scannable. The core return statement is front-loaded; while the paid-call details are lengthy, they are necessary for safe invocation.

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?

Given the output schema exists and annotations are uninformative, the description covers invocation intent, alternatives, limitations, cost, and side effects. No critical gap remains for an agent to decide to call and understand consequences.

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 input schema already covers all three parameters with descriptions, defaults, patterns, and formats (100% coverage), so the description needs to add little. It reinforces the identifier can be SIREN or SIRET and that 'since' is a publication-date filter, but doesn't duplicate schema syntax.

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 ('Returns') and resource ('latest normalized public BODACC events') with input type ('French company from a SIREN or SIRET'), and gives concrete event examples. The Avoid when block distinguishes it from company/fr/risk and company/fr/profile.

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?

Explicit Use when and Avoid when sections with named alternatives (company/fr/risk, company/fr/profile) and selection criteria. Limitations section adds boundary for when results are not appropriate.

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

All HelpMyAgent toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources