Skip to main content
Glama

HelpMyAgent

by io.github.helpmyagent
OverviewDiscussionsAdmin

French Company Changes

company_fr_changes

Returns explicit historized Sirene change flags for a French legal unit, with the normalized state that became effective on each change date. Use when: You need explainable administrative changes recorded in historized Sirene periods for one company. Avoid when: You need BODACC legal notices; use company/fr/events or company/fr/legal-announcements-search. Limitations: Only change flags explicitly provided by Sirene are returned; business events are not inferred. Sirene exposes one change indicator for the three usual-denomination fields; when it changes, the post-change values of all three fields are returned. Price: 0.015 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 changes to return, up to 100
sinceNoOptional inclusive change start date
untilNoOptional inclusive change end date
offsetNoZero-based offset within the filtered change list; use next_offset to continue
identifierYes9-digit SIREN or 14-digit SIRET

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitYesStructured value returned for “limit” as defined by this API contract.
sinceYesStructured value returned for “since” as defined by this API contract.
sirenYesNormalized 9-digit French SIREN when available.
untilYesStructured value returned for “until” as defined by this API contract.
existsYesWhether the requested company or public record was found in the checked source.
offsetYesStructured value returned for “offset” as defined by this API contract.
changesYesStructured value returned for “changes” as defined by this API contract.
truncatedYesWhether additional matching records existed beyond the returned result limit.
identifierYesIdentifier supplied for the request, echoed in normalized form when applicable.
limitationsNoKnown interpretation, source-coverage or freshness limitations for this result.
next_offsetYesStructured value returned for “next offset” as defined by this API contract.
total_countYesTotal number of matching records reported by the source or endpoint.
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. Changed1 schema field changed
    • changedOutput schema / required
      Previous value: -[
-  "identifier",
-  "identifier_type",
-  "siren",
-  "exists",
-  "since",
-  "until",
-  "offset",
-  "next_offset",
-  "limit",
-  "total_count",
-  "returned_count",
-  "truncated",
-  "changes",
-  "limitations"
-]New value: +[
+  "identifier",
+  "identifier_type",
+  "siren",
+  "exists",
+  "since",
+  "until",
+  "offset",
+  "next_offset",
+  "limit",
+  "total_count",
+  "returned_count",
+  "truncated",
+  "changes"
+]
  2. Added

TDQS

A4.7/5.0
Behavior5/5

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

Annotations are all false, so the description carries the full burden of disclosing side effects. It clearly states that source records are not modified, that a successful paid invocation can consume payment, that the payment challenge is free, and that repeating the call may require new payment. It also documents accepted x402 networks. This is strong behavioral disclosure beyond the annotations, and there is no contradiction: the non-read-only annotation is consistent with the payment side effect.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The core behavior is front-loaded in the first sentence, and the remaining sections are compact and purposeful: use/avoid guidance, limitations, price, paid-call behavior, and accepted networks. Every sentence carries decision-relevant information without filler.

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?

The tool has a well-documented input schema and an output schema, and the description adds the missing operational context: when to use it, when not to, what limitations apply, what the call costs, and what side effects occur. An agent has everything needed to select and invoke this tool correctly.

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 coverage is 100%, with all five parameters already documented in the input schema, so the description does not need to re-explain them. The caveat about the single change indicator covering three denomination fields is useful for interpreting returned state, but it does not add meaning to the input parameters themselves. Baseline 3 is appropriate.

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 opens with a specific verb and resource: 'Returns explicit historized Sirene change flags for a French legal unit, with the normalized state that became effective on each change date.' It clearly differentiates itself from BODACC-related siblings by naming company/fr/events and company/fr/legal-announcements-search.

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?

The description provides explicit 'Use when' and 'Avoid when' guidance, including specific alternative tools. It also adds a limitation note explaining that only explicitly provided Sirene flags are returned, preventing an agent from over-interpreting the result set.

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