Skip to main content
Glama

supplemental.pl — EU/PL food law

Search supplemental.pl knowledge articles

search_articles
Read-onlyIdempotent

Full-text search of supplemental.pl knowledge articles on EU/PL food law (health claims, novel food, supplements, labelling, CJEU case law) in Polish, English or German. Returns titles, URLs, dates, summaries and language versions. Example: query "novel food NMN", lang "en".

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "lang": "en",
      "query": "novel food NMN"
    },
    "name": "search_articles"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNoResponse language. Default: en.
limitNoMax results (default 5).
queryYesSearch terms, e.g. "novel food NMN" or "oświadczenia zdrowotne witamina D".

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / examples
      Added value: +[
      +  {
      +    "lang": "en",
      +    "query": "novel food NMN"
      +  }
      +]
    • addedInput schema / properties / lang / examples
      Added value: +[
      +  "en",
      +  "pl"
      +]
    • addedInput schema / properties / query / examples
      Added value: +[
      +  "novel food NMN",
      +  "oświadczenia zdrowotne witamina D"
      +]
  2. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds value beyond that by enumerating the return payload (titles, URLs, dates, summaries, language versions), which matters because there is no output schema.

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?

Two tight sentences with the resource and scope front-loaded, followed by a concrete example. The example largely duplicates the schema's own examples, which is the only redundancy.

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 domain, languages, and return fields adequately. It stops short of noting result limits or ranking behavior, but the limit parameter is documented in the schema.

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 three parameters are already documented with examples and defaults. The description only restates the language set and repeats an example query, adding little beyond the schema; baseline 3 applies.

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?

States a specific verb (full-text search) and a specific resource (supplemental.pl knowledge articles) and scopes the subject matter to EU/PL food law topics and three languages. An agent can distinguish this from get_article (single-article retrieval) or search_claims_foodlaw (claims-specific search) without opening the schema.

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 by the domain scope and the worked example, but there is no explicit when-to-use guidance and no mention of when to prefer a sibling such as get_article or search_claims_foodlaw. The agent must infer the boundary from the topic list alone.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources