Skip to main content
Glama

supplemental.pl — EU/PL food law

Get a supplemental.pl article

get_article
Read-onlyIdempotent

Return one supplemental.pl knowledge article by URL or slug: summary, headings, a text excerpt, legal references named in it and its PL/EN/DE versions. Pass lang to get another language version. Example: url "novel-food-food-supplements-eu" (slug) or the full URL https://supplemental.pl/en/knowledge/novel-food-food-supplements-eu/.

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": {
      "url": "novel-food-food-supplements-eu",
      "lang": "en"
    },
    "name": "get_article"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesArticle URL on supplemental.pl or its slug, e.g. "novel-food-food-supplements-eu".
langNoResponse language. Default: en.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / examples
      Added value: +[
      +  {
      +    "lang": "en",
      +    "url": "novel-food-food-supplements-eu"
      +  }
      +]
    • addedInput schema / properties / lang / examples
      Added value: +[
      +  "en",
      +  "pl"
      +]
    • changedInput schema / properties / url / description
      Previous value: -"Article URL on supplemental.pl or its slug."New value: +"Article URL on supplemental.pl or its slug, e.g. \"novel-food-food-supplements-eu\"."
    • addedInput schema / properties / url / examples
      Added value: +[
      +  "novel-food-food-supplements-eu",
      +  "https://supplemental.pl/en/knowledge/novel-food-food-supplements-eu/"
      +]
  2. First observed

TDQS

A3.8/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 genuine value beyond that by disclosing the shape of the response (summary, headings, excerpt, legal references, PL/EN/DE versions) and the effect of the lang parameter.

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 sentences, front-loaded with the action and return contents, followed by the lang hint and a concrete example. The example partially 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?

With no output schema, the description carries the burden of describing return values and does so adequately by listing the fields returned. Minor gaps remain around behavior for an unknown slug or URL outside supplemental.pl, but nothing essential to a correct call is missing.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description goes further by showing both accepted identifier forms (bare slug and full URL) and explaining that lang selects a different language version of the same article rather than filtering results.

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?

States a specific verb and resource ('Return one supplemental.pl knowledge article by URL or slug') and enumerates the payload (summary, headings, excerpt, legal references, language versions). It implicitly separates itself from search_articles by emphasizing single-article retrieval by identifier, though it never names the sibling explicitly.

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 only implied: an agent can infer this is for fetching a known article when it has a URL or slug. There is no explicit when-to-use/when-not guidance and no pointer to search_articles for discovery, so the routing decision is left to inference.

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