Skip to main content
Glama

HelpMyAgent

by io.github.helpmyagent
OverviewDiscussionsAdmin

French director mandates

company_fr_director_mandates

Searches public French company director mandates by name. Name matching can include homonyms and does not prove identity. Use when: Searches public French company director mandates by name. Name matching can include homonyms and does not prove identity. You know a director name and want public French company mandates associated with that name. You need candidate company links before manually resolving a person’s identity. Avoid when: You already know the company and need its current listed directors; use company/fr/directors. You need identity proof, beneficial ownership or personal contact information. Limitations: Name-based matching can include homonyms and does not prove that records refer to the same natural person. Returned mandates depend on the public company records available to the source. 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
pageNoOne-based result page number. (minimum 1; default 1).
limitNoMaximum number of records returned by this call. (minimum 1; maximum 25; default 25).
last_nameYesDirector family name to search in public French company mandates; name matching can include homonyms. (minimum length 2).
first_namesNoOptional first name or given names used to narrow director-mandate matches.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageYesStructured value returned for “page” as defined by this API contract.
limitYesStructured value returned for “limit” as defined by this API contract.
mandatesYesStructured value returned for “mandates” as defined by this API contract.
last_nameYesStructured value returned for “last name” as defined by this API contract.
first_namesYesStructured value returned for “first names” as defined by this API contract.
limitationsNoKnown interpretation, source-coverage or freshness limitations for this result.
total_companiesYesStructured value returned for “total companies” as defined by this API contract.
returned_mandatesYesStructured value returned for “returned mandates” as defined by this API contract.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / required
      Previous value: -[
-  "last_name",
-  "first_names",
-  "page",
-  "limit",
-  "total_companies",
-  "returned_mandates",
-  "mandates",
-  "limitations"
-]New value: +[
+  "last_name",
+  "first_names",
+  "page",
+  "limit",
+  "total_companies",
+  "returned_mandates",
+  "mandates"
+]
  2. Changed14 schema fields changed
    • addedInput schema / description
      Added value: +"Structured input parameters for the company/fr/director-mandates API."
    • addedInput schema / properties / first_names / description
      Added value: +"Optional first name or given names used to narrow director-mandate matches."
    • addedInput schema / properties / last_name / description
      Added value: +"Director family name to search in public French company mandates; name matching can include homonyms. (minimum length 2)."
    • addedInput schema / properties / limit / description
      Added value: +"Maximum number of records returned by this call. (minimum 1; maximum 25; default 25)."
    • addedInput schema / properties / page / description
      Added value: +"One-based result page number. (minimum 1; default 1)."
    • addedOutput schema / description
      Added value: +"Structured result returned by the company/fr/director-mandates API."
    • changedOutput schema / properties / first_names
      Previous value: -[]New value: +{
+  "description": "Structured value returned for “first names” as defined by this API contract."
+}
    • addedOutput schema / properties / last_name / description
      Added value: +"Structured value returned for “last name” as defined by this API contract."
    • addedOutput schema / properties / limit / description
      Added value: +"Structured value returned for “limit” as defined by this API contract."
    • addedOutput schema / properties / limitations / description
      Added value: +"Known interpretation, source-coverage or freshness limitations for this result."
    • addedOutput schema / properties / mandates / description
      Added value: +"Structured value returned for “mandates” as defined by this API contract."
    • addedOutput schema / properties / page / description
      Added value: +"Structured value returned for “page” as defined by this API contract."
    • addedOutput schema / properties / returned_mandates / description
      Added value: +"Structured value returned for “returned mandates” as defined by this API contract."
    • addedOutput schema / properties / total_companies / description
      Added value: +"Structured value returned for “total companies” as defined by this API contract."
  3. Added

TDQS

A4.2/5.0
Behavior4/5

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

Although readOnlyHint is false, the description explains that source records are not modified but paid invocations consume x402 payment, and it warns about homonyms and identity ambiguity. This adds useful context beyond the annotations without contradicting them.

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

Conciseness3/5

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

The description is organized into clear sections but is somewhat repetitive: the opening sentence is duplicated verbatim at the start of the 'Use when' section. It remains readable but contains avoidable redundancy.

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?

With an output schema present and explicit guidance on use cases, limitations, payment behavior, and alternatives, the agent has the key information needed to call the tool correctly. The response structure is left to the output schema, which is appropriate.

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 documents all four parameters with descriptions and constraints, so schema coverage is 100%. The description adds only marginal meaning by emphasizing last_name as the search key and first_names as an optional narrowing field.

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 states a specific verb and resource: 'Searches public French company director mandates by name.' It also explicitly contrasts itself with company/fr/directors, making the tool's scope and boundaries clear to an agent.

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' sections, naming the alternative company/fr/directors and listing exclusions such as identity proof, beneficial ownership, and contact information. This provides actionable routing criteria.

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