HelpMyAgent

Public-data KYB dossier

company_fr_kyb

Aggregates public identity, directors, financials, legal-risk and compliance checks into one informational KYB dossier. Use when: Aggregates public identity, directors, financials, legal-risk and compliance checks into one informational KYB dossier. Avoid when: Do not use this endpoint as a legal, regulated credit or guaranteed fraud-free decision unless explicitly stated otherwise. Limitations: Coverage depends on the public sources listed for this endpoint. Price: 0.050 USD per call via x402.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`domain`	No
`identifier`	Yes

Output Schema

TableJSON Schema

Name	Required	Description	Default
`name`	Yes
`siren`	Yes
`exists`	Yes
`coverage`	Yes
`sections`	Yes
`checked_at`	Yes
`identifier`	Yes
`limitations`	Yes
`identifier_type`	Yes

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

AddedSep 6, 2026

TDQS

B3.4/5.0

Behavior4/5

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

Annotations provide readOnlyHint=false, but the description adds meaningful behavioral context: it is informational, should not be used for regulated decisions, coverage depends on public sources, and it costs 0.050 USD. These details go beyond the structured annotations and help set expectations about reliability and cost.

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 compact and uses labeled sections (Use when, Avoid when, Limitations, Price), which aids scanning. However, the 'Use when' line repeats the first sentence verbatim, wasting words without adding new information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The presence of an output schema covers return-value expectations, and the description includes limitations and price. However, the complete absence of parameter semantics is a major gap for a tool with only two inputs, and the description does not clarify how to choose between 'identifier' and 'domain'.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, and the description offers no explanation of the two parameters. The required 'identifier' has a numeric pattern but no stated meaning (e.g., SIREN/SIRET or company registration number), and 'domain' is similarly unexplained. An agent cannot infer correct values from the description alone.

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 ('Aggregates') and names the exact resource categories (public identity, directors, financials, legal-risk, compliance checks) that combine into one KYB dossier. This clearly distinguishes it from sibling tools like company_fr_financials or company_fr_risk, which focus on individual components.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The 'Use when' section only restates the tool's purpose rather than giving situational guidance or pointing to specific siblings. The 'Avoid when' caveat about legal/regulated decisions is useful, but there is no explicit direction for when to choose this aggregate dossier over, say, company_fr_profile or company_fr_compliance.

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

All HelpMyAgent tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

B3.3/5.0

Disambiguation3/5

Most endpoints target distinct resources, but several clusters are easy to confuse: company_fr_intelligence vs company_fr_kyb, company_fr_peers vs company_fr_competitors vs company_fr_public_contract_competitors, and company_fr_risk vs company_fr_default_score vs company_fr_payment_context. The descriptive names help, but the repetitive 'Use when' sections often restate the description rather than contrasting with nearby tools.

Naming Consistency4/5

The dominant convention is domain_fr_feature with consistent snake_case, e.g., company_fr_profile, company_fr_financials, company_fr_public_contracts, procurement_fr_search, which makes the family predictable. The three meta tools (describe_api, list_categories, search_apis) switch to a bare verb_noun style, and a few company_fr names use verbs while most use nouns, creating a minor inconsistency.

Tool Count2/5

With 30 tools, the surface exceeds the 25+ threshold and feels heavy for an agent to navigate, especially because aggregators like company_fr_intelligence and company_fr_kyb overlap with many single-purpose endpoints. The broad French-company data domain justifies a large number of endpoints, but several could be consolidated or split out to make the server more focused.

Completeness4/5

The set covers discovery, verification, profile, directors, financials, legal risk, compliance, public contracts, procurement, funding, benchmarking, signals, and aggregation, so core French-company workflows have no major dead ends. Minor gaps remain around beneficial-ownership/shareholder data and subscription-style monitoring, but those are explicitly outside the stated scope of most endpoints.

Resources

Need Help?