SiteCheck Company Records

Employer profiles from Welcome to the Jungle: name

b2b_welcometothejungle_companies

Read-only

Employer profiles from Welcome to the Jungle (about 17,000 companies, mostly France and Europe): name, sectors, size band and employee count, offices (city, region, country, headquarters flag), open jobs count, tech stack, labels/certifications, short description, accepts spontaneous applications, logo and profile URL; plus the number of matches. Search by keyword, filter by office country and hiring-now. Related tools on this server, for a different need: b2b_brreg_norway_companies when you need Norway Business Register: searches companies by name; b2b_finland_ytj_companies when you need Finland YTJ business register: searches companies by name. Price: $0.002 in USDC per successful call, paid with x402 (Base, Solana or Arc); failed calls are not charged.

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": "b2b_welcometothejungle_companies"
  }
}

Input Schema

Name	Required	Description
`q`	No	Keyword, e.g. data, fintech, Doctolib (default all)
`page`	No	Page number from 1 (default 1)
`limit`	No	Companies per page, 1 to 50 (default 20)
`hiring`	No	true for companies with open jobs
`country`	No	Optional 2-letter country code of an office, e.g. FR, ES, CZ
`language`	No	Language for labels and descriptions: en (default), fr, es, cs, sk

Output Schema

Name	Required	Description	Default
`q`	No
`page`	No
`count`	No
`total`	No
`source`	No
`country`	No
`checkedAt`	No
`companies`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 23, 2026

TDQS

A4.2/5.0

Behavior5/5

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

Goes well beyond the readOnlyHint/openWorldHint annotations: discloses dataset size and geographic skew, notes the response includes a match count, and states pricing ($0.002 USDC per successful call via x402 on Base, Solana or Arc) with the key detail that failed calls are not charged. Cost and settlement behavior are exactly what an agent needs before invoking a paid tool.

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?

Front-loads the resource and scope well, but the long comma-separated inventory of returned fields duplicates the output schema, and the routing clause names only two of dozens of siblings in a somewhat verbose form. Information density is high but includes material that structured fields already carry.

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 full schema coverage, the description fills the remaining gaps: dataset coverage, field highlights, alternative tools, and pricing. It could note pagination/limit defaults, but those are covered by the schema, so nothing essential 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%, so parameters are already documented with examples (e.g., q 'data, fintech, Doctolib'; country 'FR, ES, CZ'). The description restates keyword/country/hiring filters without adding syntax or constraint detail beyond the schema, 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 resource (employer profiles from Welcome to the Jungle) with concrete scope (~17,000 companies, France/Europe) and enumerates the returned fields, then names the retrieval operations (keyword search, office-country filter, hiring-now filter). An agent can distinguish this from register-style siblings immediately.

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?

Explicitly routes to alternatives with a stated condition: 'b2b_brreg_norway_companies when you need Norway Business Register' and 'b2b_finland_ytj_companies when you need Finland YTJ business register.' The when-to-use for this tool itself is only implied via the field list and filters, and no exclusions (e.g., when not to use it) are given.

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

All SiteCheck Company Records tools Inspect

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

Need Help?