Skip to main content
Glama

supplemental.pl — EU/PL food law

Polish GIS notification of a food supplement — steps

gis_notification_steps
Read-onlyIdempotent

Step-by-step procedure for notifying a food supplement to the Polish Chief Sanitary Inspectorate (GIS, Art. 29–30 of the Food and Nutrition Safety Act), from the supplemental.pl article. A GIS notification is not a novel food authorisation. Example: lang "en" or "pl".

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"
    },
    "name": "gis_notification_steps"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNoResponse language. Default: en.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / examples
      Added value: +[
      +  {
      +    "lang": "en"
      +  }
      +]
    • addedInput schema / properties / lang / examples
      Added value: +[
      +  "en",
      +  "pl"
      +]
  2. First observed

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and a closed-world scope, so safety is covered structurally. The description adds that the output is a sourced procedure rather than an authorisation decision, but it says nothing about what the steps contain, how long they are, or any caveats on relying on them legally.

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?

Three sentences, front-loaded with the procedure and its legal scope, with the disambiguation early. The trailing language example is redundant given the schema and could be dropped.

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 one-optional-parameter read-only informational tool with no output schema, the description says enough to know what comes back (a notification procedure sourced from supplemental.pl) and what it is not. A brief note on the procedure's currency or jurisdictional limits would close the remaining gap.

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 coverage is 100% and the single enum parameter is fully documented in the schema, so the baseline is 3. The line "Example: lang "en" or "pl"" merely repeats the schema examples and adds no meaning about how language affects the returned procedure.

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-and-resource: step-by-step procedure for notifying a food supplement to the Polish Chief Sanitary Inspectorate, with a legal citation (Art. 29–30) and a named source article. It also explicitly disambiguates from the sibling novel_food_status by stating a GIS notification is not a novel food authorisation.

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

Usage Guidelines4/5

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

The exclusion sentence ("is not a novel food authorisation") steers the agent away from the closest-sounding sibling, which is real routing guidance. It stops short of an explicit 'use this when…' condition and doesn't mention the other article/search siblings, so a 4 rather than a 5.

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