Conecto

Size an industry by country

markets_size

Read-onlyIdempotent

An industry's size by country and year from official statistics: net turnover, value added, enterprises and persons employed from Eurostat's structural business statistics (the EU, its member states and EEA countries, from 2021), and with naics the US's firms, establishments, employees, payroll and sales from the 2022 Economic Census. Each figure as published, with Eurostat's flags (estimated, confidential: never filled in), the units, sources and licenses. The UK publishes no such figures in a form that can be queried, and the reply says so. Nothing is charged when no figures come back. Costs $0.02 per call; nothing if it fails.

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": {
      "industry": "<industry>"
    },
    "name": "markets_size"
  }
}

Input Schema

Name	Required	Description
`naics`	No	A NAICS 2022 code for the US figures, e.g. 333310.
`years`	No	How many recent years.
`industry`	Yes	A NACE Rev. 2 code: a section (C), division (28), group (28.9) or class (28.93). companies_get shows a company's.
`countries`	No	Two-letter codes (DE, FR, NO...) and EU27_2020 for the whole EU; GB says what the UK publishes. EU27_2020 when left out.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 28, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Beyond the read-only and idempotent annotations, the description discloses important behavior: figures are as published, Eurostat flags are preserved and confidential values are never filled in, UK results are unavailable, no charge applies when no figures come back, and the call costs $0.02 but is free if it fails.

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?

The description is a single dense paragraph but is front-loaded with the core purpose and then layers on source, coverage, caveat, and pricing details. Most sentences earn their place, though the paragraph is packed tightly enough to be slightly harder to scan.

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

Completeness5/5

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

For a read-only data lookup tool with no output schema, the description covers the data sources, geographic coverage, time coverage, metadata behavior, confidentiality handling, UK limitation, and pricing. An agent has enough context to know what will be returned and when results may be unavailable.

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?

The input schema has full description coverage for all four parameters, so the baseline is 3. The description reinforces the naics-to-US-source mapping and gives coverage context, but it does not add substantial parameter semantics beyond what the schema already provides.

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 states a specific verb and resource: sizing an industry by country and year from official statistics. It also names the exact sources and coverage, making it clearly distinct from sibling tools such as markets_prices, markets_products, and companies_estimate.

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?

Usage context is clear: it is for Eurostat structural business statistics in the EU/EEA from 2021, and for US 2022 Economic Census figures when a NAICS code is supplied. It also states that the UK has no queryable equivalent. It does not explicitly compare against sibling alternatives, so it stops short of a 5.

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

All Conecto 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?