Skip to main content
Glama

HelpMyAgent

by io.github.helpmyagent
OverviewDiscussionsAdmin

French Lobbying Public Profile

company_fr_lobbying

Checks the HATVP public lobbying register by French company identifier and extracts declared topics. Use when: Find the public lobbying profile declared for a French organization. You need the public HATVP lobbying-register profile associated with a French organization. You want declared lobbying topics, domains or clients when exposed by that public source. Avoid when: You need ordinary company identity, directors or ownership information; use company/fr/profile or company/fr/directors. You need lobbying information not covered by the French HATVP public register. Limitations: Coverage is limited to declarations exposed by the HATVP public lobbying dataset. A missing record does not prove that an organization has never undertaken any influence-related activity. 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
identifierYesFrench company identifier: 9-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.
existsYesWhether the requested company or public record was found in the checked source.
clientsYesStructured value returned for “clients” as defined by this API contract.
domainsYesStructured value returned for “domains” as defined by this API contract.
checked_atYesUTC timestamp at which HelpMyAgent performed the check.
identifierYesIdentifier supplied for the request, echoed in normalized form when applicable.
registeredYesStructured value returned for “registered” as defined by this API contract.
limitationsNoKnown interpretation, source-coverage or freshness limitations for this result.
declared_nameYesStructured value returned for “declared name” as defined by this API contract.
source_statusYesAvailability status of the relevant upstream public source. (allowed values: ok, unavailable, not_queried).
activity_topicsYesStructured value returned for “activity topics” as defined by this API contract.
source_json_urlYesStructured value returned for “source json url” as defined by this API contract.
registration_dateYesStructured value returned for “registration date” as defined by this API contract.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / required
      Previous value: -[
-  "identifier",
-  "exists",
-  "siren",
-  "name",
-  "source_status",
-  "registered",
-  "declared_name",
-  "registration_date",
-  "activity_topics",
-  "domains",
-  "clients",
-  "source_json_url",
-  "checked_at",
-  "limitations"
-]New value: +[
+  "identifier",
+  "exists",
+  "siren",
+  "name",
+  "source_status",
+  "registered",
+  "declared_name",
+  "registration_date",
+  "activity_topics",
+  "domains",
+  "clients",
+  "source_json_url",
+  "checked_at"
+]
  2. Changed17 schema fields changed
    • addedInput schema / description
      Added value: +"Structured input parameters for the company/fr/lobbying API."
    • addedInput schema / properties / identifier / description
      Added value: +"French company identifier: 9-digit SIREN or 14-digit SIRET."
    • addedOutput schema / description
      Added value: +"Structured result returned by the company/fr/lobbying API."
    • addedOutput schema / properties / activity_topics / description
      Added value: +"Structured value returned for “activity topics” as defined by this API contract."
    • addedOutput schema / properties / checked_at / description
      Added value: +"UTC timestamp at which HelpMyAgent performed the check."
    • addedOutput schema / properties / clients / description
      Added value: +"Structured value returned for “clients” as defined by this API contract."
    • addedOutput schema / properties / declared_name / description
      Added value: +"Structured value returned for “declared name” as defined by this API contract."
    • addedOutput schema / properties / domains / description
      Added value: +"Structured value returned for “domains” 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 / limitations / description
      Added value: +"Known interpretation, source-coverage or freshness limitations for this result."
    • addedOutput schema / properties / name / description
      Added value: +"Publicly available company, person, buyer or record name for this result."
    • addedOutput schema / properties / registered / description
      Added value: +"Structured value returned for “registered” as defined by this API contract."
    • addedOutput schema / properties / registration_date / description
      Added value: +"Structured value returned for “registration date” as defined by this API contract."
    • addedOutput schema / properties / siren / description
      Added value: +"Normalized 9-digit French SIREN when available."
    • addedOutput schema / properties / source_json_url / description
      Added value: +"Structured value returned for “source json url” as defined by this API contract."
    • addedOutput schema / properties / source_status / description
      Added value: +"Availability status of the relevant upstream public source. (allowed values: ok, unavailable, not_queried)."
  3. Added

TDQS

A4.6/5.0
Behavior5/5

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

Annotations are all false, but the description provides substantial behavioral context: source records are not modified, successful calls may consume x402 payment, the payment challenge is free, and repeated calls may require new payment. It also discloses coverage limitations and the fact that a missing record does not prove absence of influence activity.

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?

The description is well-organized with clear sections for use, avoidance, limitations, price, and network support. It is somewhat longer than strictly necessary and contains minor redundancy between the opening sentence and the Use when section, but every section contributes practical guidance.

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 paid-call behavior, network restrictions, and the tool's purpose, the description is complete. It covers what the tool checks, when to use it, when to avoid it, pricing, payment behavior, and data limitations. The output schema covers return details, so the description does not need to.

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 fully documents the single required parameter, including the 9-digit SIREN or 14-digit SIRET pattern. The description adds no additional parameter-level meaning beyond what the schema provides, so the baseline of 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?

The description uses a specific verb and resource: "Checks the HATVP public lobbying register by French company identifier and extracts declared topics." It clearly distinguishes this tool from sibling tools by naming alternatives for ordinary identity and directors information.

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 includes explicit "Use when" and "Avoid when" guidance, naming concrete alternative tools such as company/fr/profile and company/fr/directors. It also states when not to use the tool, covering the key selection decision an agent needs.

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