Reecopedia

Search EU textile regulations

search_eu_textile_regulations

Read-onlyIdempotent

Search regulatory evidence in English legal register. Cite original document and unit; verify each claim. Optional scope narrows corpus partitions. No model assesses the answer in this MCP tool; the client must verify each claim against the returned text. Query embeddings use Alibaba; candidate passages are sent to Jina for reranking.

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": {
      "query": "<query>"
    },
    "name": "search_eu_textile_regulations"
  }
}

Input Schema

Name	Required	Description	Default
`query`	Yes
`scope`	No
`top_k`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedSep 17, 2026

removedInput schema / properties / query / description

Removed value: -"English, in the legal register of the act. A non-English query is accepted but retrieves poorly, and the result then carries a `notice` saying so.\nAct identifiers stay verbatim (\"ESPR\", \"2024/1781\"): they are\nmatched as metadata. Article and annex numbers are matched in\ntheir English form: \"第9条\" and \"Artikel 9\" do not match,\n\"Article 9\" does.\nMeasured 2026-08-27 on the live index, one question three ways:\n\"must a marketplace show the product passport before purchase,\nwhere is it written?\" returned NOTHING; \"marketplace must make the\ndigital product passport accessible before purchase\" returned the\nCWA guidance (0.96) with the ESPR at 0.001; \"make the digital\nproduct passport accessible to customers before they are bound by a\ncontract of sale\" returned the ESPR itself first (0.94, p.21)."

addedInput schema / properties / scope

Added value: +{
+  "anyOf": [
+    {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null
+}

changedInput schema / properties / top_k / default
```
Previous value: -10New value: +20
```

removedInput schema / properties / top_k / description

Removed value: -"Number of passages to return (1-10, default 10)."

Changed1 schema field changedSep 7, 2026

changedInput schema / properties / query / description

Previous value: -"ENGLISH ONLY, in the legal register of the act. A non-English `query` violates this tool's contract and its passages must be discarded, not answered from.\nAct identifiers stay verbatim (\"ESPR\", \"2024/1781\"): they are\nmatched as metadata. Article and annex numbers must be rewritten\ninto their English form, because that is how they are matched:\n\"第9条\" and \"Artikel 9\" do not match, \"Article 9\" does.\nMeasured 2026-08-27 on the live index, one question three ways:\n\"must a marketplace show the product passport before purchase,\nwhere is it written?\" returned NOTHING; \"marketplace must make the\ndigital product passport accessible before purchase\" returned the\nCWA guidance (0.96) with the ESPR at 0.001; \"make the digital\nproduct passport accessible to customers before they are bound by a\ncontract of sale\" returned the ESPR itself first (0.94, p.21)."New value: +"English, in the legal register of the act. A non-English query is accepted but retrieves poorly, and the result then carries a `notice` saying so.\nAct identifiers stay verbatim (\"ESPR\", \"2024/1781\"): they are\nmatched as metadata. Article and annex numbers are matched in\ntheir English form: \"第9条\" and \"Artikel 9\" do not match,\n\"Article 9\" does.\nMeasured 2026-08-27 on the live index, one question three ways:\n\"must a marketplace show the product passport before purchase,\nwhere is it written?\" returned NOTHING; \"marketplace must make the\ndigital product passport accessible before purchase\" returned the\nCWA guidance (0.96) with the ESPR at 0.001; \"make the digital\nproduct passport accessible to customers before they are bound by a\ncontract of sale\" returned the ESPR itself first (0.94, p.21)."

Changed1 schema field changedAug 27, 2026

changedInput schema / properties / query / description

Previous value: -"The regulatory question — SEND IT IN ENGLISH even if the user\nasked in another language, whatever that language is (the corpus is\nEnglish; a non-English query can miss the official text entirely),\nthen answer the user in their own language. Do NOT translate\nword-for-word: phrase it in the LEGAL REGISTER of the act, because\nretrieval matches the wording of the law, not the phrasing of the\nquestion. Measured 2026-08-27 on the live index, same question three\nways: \"must a marketplace show the product passport before purchase,\nwhere is it written?\" returned NOTHING; \"marketplace must make the\ndigital product passport accessible before purchase\" returned the\nCWA guidance (0.96) with the ESPR at 0.001; \"make the digital\nproduct passport accessible to customers before they are bound by a\ncontract of sale\" returned the ESPR itself first (0.94, p.21). Keep\narticle/annex numbers and act identifiers verbatim (\"Article 9\",\n\"ESPR\", \"2024/1781\"): those are matched as metadata, not translated."New value: +"ENGLISH ONLY, in the legal register of the act. A non-English `query` violates this tool's contract and its passages must be discarded, not answered from.\nAct identifiers stay verbatim (\"ESPR\", \"2024/1781\"): they are\nmatched as metadata. Article and annex numbers must be rewritten\ninto their English form, because that is how they are matched:\n\"第9条\" and \"Artikel 9\" do not match, \"Article 9\" does.\nMeasured 2026-08-27 on the live index, one question three ways:\n\"must a marketplace show the product passport before purchase,\nwhere is it written?\" returned NOTHING; \"marketplace must make the\ndigital product passport accessible before purchase\" returned the\nCWA guidance (0.96) with the ESPR at 0.001; \"make the digital\nproduct passport accessible to customers before they are bound by a\ncontract of sale\" returned the ESPR itself first (0.94, p.21)."

Changed1 schema field changedAug 27, 2026

changedInput schema / properties / query / description

Previous value: -"The regulatory question — SEND IT IN ENGLISH even if the user\nasked in another language (the corpus is English; a non-English\nquery can miss the official text entirely), then answer the user in\ntheir own language. Keep article/annex numbers and act identifiers\nverbatim (\"Article 9\", \"ESPR\", \"2024/1781\"): those are matched as\nmetadata, not translated."New value: +"The regulatory question — SEND IT IN ENGLISH even if the user\nasked in another language, whatever that language is (the corpus is\nEnglish; a non-English query can miss the official text entirely),\nthen answer the user in their own language. Do NOT translate\nword-for-word: phrase it in the LEGAL REGISTER of the act, because\nretrieval matches the wording of the law, not the phrasing of the\nquestion. Measured 2026-08-27 on the live index, same question three\nways: \"must a marketplace show the product passport before purchase,\nwhere is it written?\" returned NOTHING; \"marketplace must make the\ndigital product passport accessible before purchase\" returned the\nCWA guidance (0.96) with the ESPR at 0.001; \"make the digital\nproduct passport accessible to customers before they are bound by a\ncontract of sale\" returned the ESPR itself first (0.94, p.21). Keep\narticle/annex numbers and act identifiers verbatim (\"Article 9\",\n\"ESPR\", \"2024/1781\"): those are matched as metadata, not translated."

Changed1 schema field changedAug 27, 2026

changedInput schema / properties / query / description

Previous value: -"The regulatory question, in any language (English works best)."New value: +"The regulatory question — SEND IT IN ENGLISH even if the user\nasked in another language (the corpus is English; a non-English\nquery can miss the official text entirely), then answer the user in\ntheir own language. Keep article/annex numbers and act identifiers\nverbatim (\"Article 9\", \"ESPR\", \"2024/1781\"): those are matched as\nmetadata, not translated."

Changed2 schema fields changedJul 16, 2026

changedInput schema / properties / top_k / default
```
Previous value: -6New value: +10
```

changedInput schema / properties / top_k / description

Previous value: -"Number of passages to return (1-10, default 6)."New value: +"Number of passages to return (1-10, default 10)."

First observedJul 12, 2026

TDQS

A3.7/5.0

Behavior5/5

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

The description adds substantial behavioral context beyond the readOnly/idempotent annotations: 'No model assesses the answer in this MCP tool; the client must verify each claim against the returned text.' It also discloses the underlying processing pipeline ('Query embeddings use Alibaba; candidate passages are sent to Jina for reranking'). This is exactly the kind of grounding an agent needs for a search tool.

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 five sentences, front-loaded with purpose ('Search regulatory evidence in English legal register') and each sentence contributes distinct value. Slight redundancy exists with 'verify each claim' appearing twice, but overall it is efficient and structured.

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?

The description covers the core function, the scope parameter, the client-verification requirement, and the reranking pipeline. An output schema exists, so return-value details are not required. Minor ambiguity remains about whether the corpus is specifically EU textile regulations, but the title and tool name resolve that; top_k is also not explained in prose, but the schema provides a default.

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

Parameters2/5

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

The input schema has 0% description coverage, so the description must compensate for parameter meaning. It explains only one of three parameters: 'Optional scope narrows corpus partitions.' The 'query' parameter is left to obvious inference, and 'top_k' receives no explanation at all, leaving its semantics (e.g., number of results) to the agent. This is insufficient given the low schema coverage.

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 verb and resource: 'Search regulatory evidence in English legal register.' It also adds operational detail by instructing to 'Cite original document and unit; verify each claim.' This distinguishes the tool from generic siblings like 'search' through the legal-register scope, though it does not explicitly mention 'EU textile' in the description (the title and name do).

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 context by defining the search domain and noting 'Optional scope narrows corpus partitions,' which is a usage hint. However, it does not explicitly state when to prefer this tool over alternatives like the sibling 'search' or 'find_exact_text,' nor does it provide exclusions or when-not conditions.

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

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