Skip to main content
Glama

Jecfa Functional Classes

jecfa_functional_classes
Read-onlyIdempotent

List the JECFA functional-class vocabulary, the 71 technological purposes a substance can be evaluated under (sweetener, emulsifier, antioxidant, humectant...), grouped into food additives, flavouring agents, food contaminants and veterinary drugs. Call this to discover the exact class name that jecfa_by_functional_class expects.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so safety is covered structurally. The description adds genuine context beyond them by describing the payload shape: a vocabulary of 71 entries, with example values and a four-way grouping into food additives, flavouring agents, food contaminants and veterinary drugs. It does not state the exact return format, but for a small static lookup that is a minor gap.

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?

Two sentences, front-loaded with the verb and resource, then the concrete detail (71, examples, four categories), then the routing instruction. Every clause carries information; no filler or restatement 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?

There is no output schema, so the description must convey what comes back, and it does: a class vocabulary with count, examples and grouping. The only omission is a precise statement of the entry structure (name-only vs. name plus group), which would fully close the loop for an agent parsing results.

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?

The tool takes zero parameters, so the baseline is 4; there is nothing for the description to disambiguate. It does not mislead about inputs, and the empty object schema is consistent with the description's framing as a pure enumeration call.

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 the JECFA functional-class vocabulary"), quantifies the scope (71 technological purposes, with concrete examples like sweetener, emulsifier, antioxidant), and names the grouping scheme into four categories. An agent can distinguish it immediately from jecfa_by_functional_class, which consumes these class names rather than listing them.

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

Usage Guidelines5/5

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

Explicitly prescribes when to call it: "Call this to discover the exact class name that jecfa_by_functional_class expects." That names the alternative sibling and the precondition that selects this tool, leaving nothing 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.