Trade Intelligence

Import market figures

product_market

Read-only

The import market for a product, from government trade statistics: how much the US, UK, Canada and Germany import of its HS6 code (from China and from the world, China's share, 2024 and 2025), how many UK and Canadian companies import it, and the unit price Chile's importers declared for it from China in 2025. Each figure has its source and link. Free; does not spend a search.

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": {
      "product": "<product>"
    },
    "name": "product_market"
  }
}

Input Schema

Name	Required	Description	Default
`product`	Yes	Product words, e.g. 'cookware set'

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 9, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already declare a safe read (readOnlyHint=true) against a closed data source (openWorldHint=false). Beyond that, the description adds two things annotations cannot: every returned figure carries its source and link, and the call is free / does not consume a search quota. It stops short of describing failure behavior for unresolvable products.

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?

One dense but well-ordered sentence that front-loads the purpose and then enumerates the returned figures, followed by a short clause on sourcing and cost. Every clause carries information; the nested parenthetical list is slightly heavy but not padded.

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?

No output schema exists, so the description carries the return-value burden itself, and it does so by enumerating the exact figure set and noting source links. For a read-only, single-parameter lookup that is close to complete; only edge-case behavior for unmatched products 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?

With 100% schema coverage on a single parameter, the schema already explains 'product words'. The description adds the meaningful detail that the product is resolved to an HS6 code, which implies code resolution happens internally, but says nothing about ambiguity, partial matches, or how to phrase qualifying input.

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 precisely: import market figures per HS6 code, with the exact countries (US, UK, Canada, Germany), origins (China vs world), years (2024/2025), company counts and a Chile declared unit price. That is far beyond a title restatement. It does not explicitly contrast itself with siblings such as price_bands or get_suppliers, so it falls short of a 5.

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?

Usage is implied rather than stated: an agent can infer 'reach for this when you need import demand/size data for a product'. The phrase 'Free; does not spend a search' hints at a cost model versus search-based siblings, but no alternative is named and no 'use this instead when...' condition is given.

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

All Trade Intelligence 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?