Skip to main content
Glama

Insee

by io.github.pipeworx-io

Insee Company

insee_company
Read-onlyIdempotent

Look up a French company or establishment in INSEE's official SIRENE business registry. PREFER OVER WEB SEARCH for "who is French company X", "details for SIREN/SIRET …", legal name, activity (NAF/APE code), address, headcount band, creation date, active/ceased status. Pass a 9-digit SIREN (legal unit) or 14-digit SIRET (establishment).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
_apiKeyNoOptional — your own INSEE SIRENE API key. Omit to use the shared Pipeworx key.
identifierYesA SIREN (9 digits) or SIRET (14 digits), e.g. "552032534" (Danone).

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false. The description adds value by listing the returned data fields (legal name, NAF/APE code, address, etc.) without contradicting annotations.

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, no wasted words. First sentence states purpose and resource, second gives usage guidance and parameter format. Front-loaded with the action.

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 simple lookup tool with high schema and annotation coverage, the description is complete. It lists the fields returned, compensating for lack of output schema. Minor omission of error conditions but acceptable.

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

Parameters4/5

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

Schema covers 100% with descriptions for both parameters, including example values. The description adds context by specifying 'SIREN (legal unit) or SIRET (establishment)', which provides slightly more semantic meaning than the schema 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 clearly states it looks up French companies/establishments in the official SIRENE registry, with specific verb 'Look up' and resource. It distinguishes from web search by explicitly saying 'PREFER OVER WEB SEARCH', and the sibling tools include other lookup tools making this differentiation valuable.

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

Usage Guidelines4/5

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

The description explicitly says to prefer over web search for specific queries like 'who is French company X' and lists attributes it can provide. It implies when to use and gives identifier format guidance, but does not contrast with sibling tools like entity_profile or resolve_entity.

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

All Insee toolsInspect
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

A3.9/5.0
Disambiguation3/5

Most tools have detailed, carve-out descriptions, but ask_pipeworx, ask_pipeworx_beta, and ask_pipeworx_grounded share the same routing core, with the beta version currently identical to the stable one. The Polymarket and company-research clusters are better differentiated, but the number of overlapping research/query entry points still creates real selection risk.

Naming Consistency3/5

The set is consistently snake_case and has coherent prefixes like ask_pipeworx_ and polymarket_, but it mixes verb_noun names (resolve_entity, scan_dependency, discover_tools) with noun-phrase names (entity_profile, bet_research, recent_changes) and one-word verbs (remember, recall, forget). The naming is readable but does not follow one predictable pattern.

Tool Count2/5

With 32 tools, the server exceeds the 25+ threshold for too many tools and feels like a broad platform dump rather than a focused toolkit. Several utility, memory, and meta-discovery tools could reasonably live in separate servers, and the Insee name makes the breadth especially unfocused.

Completeness4/5

For the broad data-research platform it actually exposes, the coverage is strong: general lookup, grounded verification, deep research, entity resolution, company profiles, comparisons, change feeds, subscriptions, and memory all have working lifecycles. The main gap is that some unrelated utilities like scan_dependency and generate_llms_txt feel tacked on rather than part of a missing core workflow.

Resources