Skip to main content
Glama

EU cosmetics regulatory status for a substance name

health_eu_cosing_cosmetics
Read-only

EU cosmetics regulatory status for a substance name: matching Annex II (prohibited), III (restricted), IV (colorants), V (preservatives) and VI (UV filters) entries of Regulation (EC) No 1223/2009 from the European Commission's CosIng database, with reference number, maximum concentration, conditions and warnings, CAS/EC numbers, amending regulation and SCCS opinions. Price: $0.002 per successful call, paid with x402 (USDC on Base, Solana and 10 more networks); failed calls are not charged.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "name": "<name>"
    },
    "name": "health_eu_cosing_cosmetics"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesSubstance or INCI name, e.g. salicylic acid (required)
limitNoEntries to return, 1 to 25 (default 10)

Output Schema

NameRequiredDescriptionDefault
countNo
queryNo
totalNo
sourceNo
entriesNo
checkedAtNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the description's job is to add context, and it does: it discloses the data source, the per-call price ($0.002), the x402 payment mechanism with networks, and that failed calls are not charged. It does not cover error modes or behavior when a name matches multiple entries, which keeps it short of a 5.

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 purpose is front-loaded in the first clause, and the dense annex/field enumeration is informative rather than padding. The pricing sentence is separate and clearly delimited, though the first sentence is long and clause-heavy.

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 an output schema present, the description need not explain return values, yet it still enumerates the returned fields (reference number, max concentration, conditions, CAS/EC, SCCS opinions). Combined with cost and source disclosure, an agent has what it needs to call this correctly; only ambiguity handling is unaddressed.

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 both the name and limit parameters are already documented in the schema, including the example and the 1-25 range. The description repeats the 'substance name' concept but adds no syntax, normalization, or INCI-vs-CAS matching detail beyond the schema, so the baseline 3 applies.

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 names a specific resource and scope: EU cosmetics regulatory status for a substance name, broken down by Annex II/III/IV/V/VI of Regulation (EC) No 1223/2009 sourced from CosIng. That is far more than a restatement of the name, but it never explicitly distinguishes itself from the sibling health_cosmetics_inci_ingredients lookup.

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

Usage Guidelines3/5

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

The purpose implies the use case (look up a substance to see if it is prohibited, restricted, or listed as a colorant/preservative/UV filter in the EU), but there is no explicit when-to-use, when-not-to-use, or named alternative. Guidance is inferred from the described data coverage rather than stated.

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.

Resources