Skip to main content
Glama

Gsfa Additive Provisions

gsfa_additive_provisions
Read-onlyIdempotent

List every food category in which a given food additive is permitted under the Codex GSFA, with the maximum use level for each. Separates Table 1 and 2 provisions (which carry a specific maximum level) from Table 3 provisions (permitted under good manufacturing practice with no numeric limit). Use to see the full permitted scope of one additive across all foods.

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": {
      "additive": "461"
    },
    "name": "gsfa_additive_provisions"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum provisions returned (default 200).
tableNoFilter to one table: "table1_2" or "table3". Omit for both.
additiveYesINS number, name, or synonym, e.g. "415", "xanthan gum".

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / additive / description
      Previous value: -"INS number, name, or synonym — e.g. \"415\", \"xanthan gum\"."New value: +"INS number, name, or synonym, e.g. \"415\", \"xanthan gum\"."
  2. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), so the description's job is to add domain behavior — which it does by explaining that Table 1/2 provisions carry a numeric maximum while Table 3 provisions are GMP with no numeric limit. That materially shapes how an agent should interpret results. It does not describe ordering, truncation behavior at the default limit of 200, or result shape.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three sentences, each earning its place: capability, result taxonomy, and usage. The core verb and resource are front-loaded with no preamble or repetition of the title.

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 list tool with full schema coverage and no output schema, the definition covers what the tool returns (categories plus maximum levels) and how the two provision families differ. Minor gaps remain around pagination/limit truncation and what a GMP entry looks like in the response.

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 baseline is 3, but the description adds real meaning to the 'table' parameter by defining what table1_2 and table3 conceptually mean (specific maximum level vs GMP with no numeric limit). The 'additive' and 'limit' parameters get no extra explanation beyond the schema.

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: 'List every food category in which a given food additive is permitted under the Codex GSFA, with the maximum use level for each.' The scope phrase 'full permitted scope of one additive across all foods' implicitly separates it from point-check siblings like gsfa_check_use, so an agent can route correctly.

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?

'Use to see the full permitted scope of one additive across all foods' gives a clear positive usage context. It never names an alternative tool or states when NOT to use it (e.g. for a single food/additive lookup), so it stops short of full routing guidance.

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.