Conecto

Track an industry's prices and costs

markets_prices

Read-onlyIdempotent

Price indices for an industry's selling prices and costs, by country and month: producer prices or import prices by NACE code, the labour cost index for its NACE section (quarterly), or electricity prices for businesses (half-yearly), from Eurostat; and US series from the BLS by series id. Each series with its values, the latest, the change on a year (a decimal: 0.021 is 2.1%), the base year and the unit. Nothing is charged when no figures come back. Costs $0.02 per call; nothing if it fails.

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

Input Schema

Name	Required	Description	Default
`months`	No	How many recent months to show.
`measure`	No	producer: selling prices at home; import: prices of imports; labour_cost: the labour cost index; energy: electricity prices.	producer
`industry`	No	A NACE Rev. 2 code: a section (C), division (28), group (28.9) or class (28.93). companies_get shows a company's. Not needed for energy.
`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.
`bls_series`	No	US series ids from the BLS, e.g. PCU333310333310 (producer prices of NAICS 333310).

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 28, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already cover read-only safety, idempotency, and open-world access. The description adds meaningful context beyond that: the pricing model ($0.02 per call, nothing if it fails or no figures return) and the shape of returned series including the decimal format for year-over-year change. It does not detail pagination or rate limits, but the added cost and return-format context is substantive.

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 dense but front-loaded with the tool's purpose, followed by return shape and pricing. Every sentence carries information; the long first sentence is somewhat heavy but not wasteful.

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 no output schema, the description takes on the burden of explaining return values, and it does so well: each series includes values, latest value, year-over-year change with decimal convention, base year, and unit. Combined with annotation coverage, this is nearly complete, though explicit sibling differentiation is absent.

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 the schema already documents all five parameters. The description adds limited extra meaning, such as noting that labour cost is quarterly and electricity prices are half-yearly, but most of its parameter-related content (NACE codes, BLS series IDs) repeats or lightly paraphrases the schema.

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?

The description states a specific resource (price indices for an industry's selling prices and costs) and specifies the sources and measures covered (Eurostat producer/import/labour cost/electricity indices, BLS series). It is clear what the tool does, but it never explicitly distinguishes itself from sibling tools like markets_products, markets_size, or valuation_benchmark.

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 enumerating the measure types and their data sources, which helps an agent pick a measure value. However, it gives no explicit guidance on when to prefer this tool over related siblings (e.g., markets_size for market sizing) and no exclusions or prerequisites are stated.

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?