Skip to main content
Glama
openapi-mcp-sdk

openapi-mcp-sdk

Search French companies by advanced criteria

get_company_FR_search
Read-onlyIdempotent

Search French companies by name, department, NAF code, or activity status. Return filtered, paginated results with optional data enrichment or a dry-run count and cost.

Instructions

Returns a list of French companies based on the search criteria. Args: companyName: The name or part of it of a French company (optional). provinceCode: The department code or region to restrict search (optional). skip: The number of records to skip for pagination (optional). limit: The maximum number of results to return (optional, default 10). dataEnrichment: Enrichment options: start, advanced, name (default is name). dryRun: Set to 1 to only get count and cost (optional). nafCode: NAF Activity Code for the company (optional). activityStatus: Status of the company (optional).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_company_FR_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
skipNo
limitNo
dryRunNo
nafCodeNo
companyNameNo
provinceCodeNo
activityStatusNo
dataEnrichmentNoname

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true and openWorldHint=false, so the safety profile is covered. The description adds two genuinely useful behaviors beyond that: limit defaults to 10 and dryRun=1 returns only count and cost. It says nothing about cost units, rate limits, or what the enriched records contain.

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?

Compact, with no wasted sentences, and the dryRun and default-limit facts are stated plainly. The Args block dumps parameters in schema order rather than ranking the ones that actually drive result cost or shape, so it is efficient but not well prioritized.

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

Completeness2/5

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

With eight optional parameters, no output schema, and an explicitly cost-gated dryRun mode, the description should explain the response shape and the count/cost workflow. It also never clarifies how the 'start'/'advanced'/'name' enrichment tiers change results, which is the main decision an agent faces here.

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 0%, so the description carries the full burden, and it does document all eight parameters. However several entries are thin: provinceCode conflates 'department code or region', dataEnrichment names three modes without explaining how they differ, and activityStatus/nafCode give no value format or accepted vocabulary.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Returns a list of French companies') and the geographic scope 'French' implicitly distinguishes it from the IT/EU/WW siblings. It does not explicitly name an alternative, but an agent can identify the country-specific search tool without opening the schema.

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

Usage Guidelines2/5

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

No guidance on when to choose this over get_company_EU_advanced or get_company_WW_advanced, nor when the 'start' vs 'advanced' enrichment tier applies. The only implied usage is the geographic scope in the name, leaving tier selection to guesswork.

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