OpenHelvetia Gateway

fedlex.search_text

Read-only

Find where a word occurs inside ONE consolidation (hits with eId and Artikel): use before read_article when the article is unknown. hint.

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": {
      "eli_version": "<eli_version>",
      "query": "<query>"
    },
    "name": "fedlex.search_text"
  }
}

Input Schema

Name	Required	Description
`lang`	No	Manifestation language (de\|fr\|it\|en\|rm); default de. Which languages a version carries as XML is the graph's answer — fedlex.list_expressions shows it before a read.
`limit`	No	Max hits (default 20, at most 100); `total` counts beyond it.
`query`	Yes	Word or phrase; case-insensitive substring.
`eli_version`	Yes	Dated consolidation: `<abstract-eli>/<YYYYMMDD>`.

Schema Changelog

Changes observed during successful MCP inspections.

First observedSep 6, 2026

TDQS

A4.3/5.0

Behavior4/5

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

The readOnlyHint annotation already covers the safety profile, lowering the bar. The description adds useful behavioral context by stating that hits contain eId and Artikel, which is essential for chaining into read_article. It does not discuss pagination or auth, but those are less critical given the annotation.

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 commendably short and front-loaded with the core action and purpose, followed by a clear usage pointer. However, the trailing lone word 'hint.' is unexplained and introduces minor ambiguity, preventing a perfect score.

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?

For a read-only search tool with no output schema, the description covers what is searched, what hits contain, and the intended workflow (preceding read_article). Required inputs are documented in the schema, and the only omissions are minor details like pagination behavior, which the schema already addresses through the limit parameter.

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 all four parameters (lang, limit, query, eli_version) are fully documented in the schema. The tool description adds no parameter-level details beyond what the schema already provides, so it remains at the baseline.

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 ('Find where a word occurs') on a bounded resource ('inside ONE consolidation') and clarifies the output ('hits with eId and Artikel'). It also distinguishes this tool from sibling read_article by explicitly naming it, making the tool's role unmistakable.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives direct, actionable routing: 'use before read_article when the article is unknown.' The 'ONE consolidation' qualifier further signals that this tool is not for cross-law search, effectively excluding that alternative.

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

All OpenHelvetia Gateway 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?