Skip to main content
Glama

Jecfa Chemical

jecfa_chemical
Read-onlyIdempotent

Fetch the complete JECFA record for one substance by its chemical id: chemical and synonym names, CAS and INS numbers, functional class, and every safety evaluation JECFA has made of it, evaluation year, ADI, the committee's conclusions, dietary exposure findings, meeting number, and the TRS report and toxicological monograph citations. Use after search to explain how and when an ADI was set or revised.

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": {
      "id": 62
    },
    "name": "jecfa_chemical"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesChemical id from jecfa_search (e.g. 62 for aspartame).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive, so the safety profile is covered. The description adds substantive context about the scope of the returned data — complete historical evaluations, ADI, conclusions, exposure, meeting number, and citations — which tells the agent this is a deep single-record fetch rather than a summary.

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?

Two sentences, front-loaded with the action and the key, followed by a field enumeration and a usage note. The long enumeration is justified because there is no output schema, though the run-on field list is dense.

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?

With no output schema, the description carries the full burden of describing return values and does so thoroughly — names, CAS/INS numbers, functional class, evaluations, ADI, conclusions, exposure, meeting number, and citations. Nothing an agent needs before calling is missing.

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 `id` parameter is documented in-schema with an example (62 for aspartame). The description reinforces that the id keys to a chemical record but adds no format or range guidance beyond the schema, so the baseline of 3 applies.

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 ("Fetch the complete JECFA record for one substance by its chemical id") and enumerates the record's contents. The phrase "by its chemical id" separates it from lookup-by-number siblings such as jecfa_by_number.

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 after search to explain how and when an ADI was set or revised" gives a clear usage context and places it downstream of jecfa_search. It stops short of naming explicit when-not conditions or a named alternative, so it falls just short of 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.