Skip to main content
Glama

Gsfa Check Use

gsfa_check_use
Read-onlyIdempotent

Answer whether a specific food additive is permitted in a specific food category under the Codex General Standard for Food Additives, and at what maximum level. Returns the maximum use level (a numeric limit such as 10,000 mg/kg, or GMP meaning good manufacturing practice), which GSFA table the permission comes from, the note references that condition it, and whether the permission was stated for that exact food category or inherited from a parent category. Use for questions about whether an additive is allowed in a food, legal use levels, and food additive compliance.

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",
      "food_category": "14.1.5"
    },
    "name": "gsfa_check_use"
  }
}

Input Schema

NameRequiredDescriptionDefault
additiveYesINS number, name, or synonym, e.g. "461", "methyl cellulose".
food_categoryYesGSFA food category number ("13.2") or its name ("complementary foods for infants"), both work. Subcategories inherit parent provisions.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / additive / description
      Previous value: -"INS number, name, or synonym — e.g. \"461\", \"methyl cellulose\"."New value: +"INS number, name, or synonym, e.g. \"461\", \"methyl cellulose\"."
    • changedInput schema / properties / food_category / description
      Previous value: -"GSFA food category number (\"13.2\") or its name (\"complementary foods for infants\") — both work. Subcategories inherit parent provisions."New value: +"GSFA food category number (\"13.2\") or its name (\"complementary foods for infants\"), both work. Subcategories inherit parent provisions."
  2. First observed

TDQS

A4.1/5.0
Behavior4/5

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

The annotations already establish that this is a read-only, idempotent, non-destructive, open-world lookup. The description adds useful behavioral detail by explaining the return values: maximum use level, GSFA table source, note references, and whether the permission is exact or inherited from a parent category. It does not discuss error cases or ambiguity handling, but it meaningfully supplements the annotations.

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?

The description is front-loaded with the core question it answers, then explains the return values, then states the use cases. It is appropriately sized for a two-parameter lookup tool and contains no redundant or filler wording.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a read-only GSFA lookup with no output schema, the description explains both the purpose and the shape of the returned information, including maximum level, table source, notes, and inheritance status. Together with the fully documented input schema and safety annotations, it gives an agent enough context to call the tool correctly.

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 the input schema already documents both parameters, including that additive can be an INS number, name, or synonym and that food_category can be a number or name. The description does not add parameter syntax or constraints beyond what the schema provides, so the baseline score of 3 is appropriate.

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?

The description states a specific verb and resource: answering whether a named food additive is permitted in a named food category and at what maximum level. It is clear and actionable, but it does not explicitly distinguish this tool from similarly named GSFA siblings such as gsfa_additive_provisions or gsfa_food_category_additives.

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?

It gives clear usage context: questions about whether an additive is allowed in a food, legal use levels, and food additive compliance. It does not state when not to use it or name alternative tools for related GSFA queries, so it falls short of full when/when-not/alternatives 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.