Skip to main content
Glama

Jecfa By Functional Class

jecfa_by_functional_class
Read-onlyIdempotent

List every substance JECFA has evaluated in one functional class, sweeteners, preservatives, colours, emulsifiers, antioxidants and so on, or every substance in one of the four groups: food_additives, flavouring_agents, food_contaminants, veterinary_drugs. Each entry carries its ADI and CAS number. Use to survey what is permitted in a category rather than to look up a single substance.

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": {
      "functional_class": "sweetener"
    },
    "name": "jecfa_by_functional_class"
  }
}

Input Schema

NameRequiredDescriptionDefault
functional_classYesClass name ("sweetener", "preservative"), group name ("food_additives"), or a numeric class id from jecfa_functional_classes.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/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 open-world, so the safety profile is covered. The description adds useful context beyond that by disclosing what each result entry carries (ADI and CAS number) and by enumerating the four top-level groups, which shapes what the agent can expect back.

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?

The core scope is front-loaded in the first clause, followed by the group enumeration and the usage sentence. The category list is a little long, but each item clarifies valid input values rather than padding, so the length is largely earned.

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 takes on the job of describing returns and does so at a high level (ADI and CAS per entry). For a single-parameter list tool that is close to sufficient; only pagination or result-size behavior is left unstated.

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. The description goes further by listing concrete accepted values (sweeteners, preservatives, colours, emulsifiers, antioxidants) and the four group names, which matters because the parameter has no enum constraint. It still doesn't clarify whether matching is case-sensitive or how the numeric class id relates to jecfa_functional_classes.

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?

The description names a specific verb and resource ("List every substance JECFA has evaluated") and scopes it to one functional class or one of four groups. It also implicitly separates itself from single-substance lookups like jecfa_by_number or jecfa_chemical, so an agent can place it without opening a schema.

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 states the intended use case explicitly: "Use to survey what is permitted in a category rather than to look up a single substance." That gives a clear when-to-use and when-not, but it does not name the sibling tool to switch to, leaving the agent to infer jecfa_chemical or jecfa_by_number.

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.