Skip to main content
Glama

France company

run_fr_companies
Read-onlyIdempotent

Get one company from the France registry (RNE / INPI) by registration number or registry URL: name, status, registration date, address and legal form. Flat 30 points per successful run.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "company": "<company>"
    },
    "name": "run_fr_companies"
  }
}

Input Schema

NameRequiredDescriptionDefault
companyYesRegistration number or registry URL. e.g. 552032534

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, openWorld). The description adds genuinely new context beyond them: the field set returned and the pricing model ('Flat 30 points per successful run'), which is a real behavioral trait. It stops short of describing failure modes (e.g. what happens if the number isn't found).

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?

Two sentences, zero filler, front-loaded with the action and the resolution key, followed by the return fields and the cost note. Every clause carries information an agent needs.

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?

For a single-parameter, single-record lookup with rich annotations and no output schema, the description supplies the source registry, the key format, the returned fields and the cost. Only the behavior on failed/ambiguous lookups is missing.

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 description coverage is 100% and the single parameter already documents 'Registration number or registry URL. e.g. 552032534'. The description restates the same dual-mode input without adding syntax, format, or edge-case handling, so baseline 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?

States a specific verb ('Get one company'), the exact resource and source registry (France registry RNE/INPI), and enumerates the returned fields. It also pins down the lookup key (registration number or registry URL), which cleanly separates it from the sibling run_fr_companies_search.

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 description implies usage by stating the accepted identifiers ('by registration number or registry URL'), which tells an agent this is a single-record lookup rather than a search. However it never explicitly names run_fr_companies_search as the alternative or states when not to use this tool, so the routing guidance is left to inference.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources