Skip to main content
Glama

BRAINIAC Product Safety & Recalls

Search EU Safety Gate alerts

product-safety_eu-safety-gate-alert
Read-onlyIdempotent

Search EU Safety Gate (RAPEX) non-food product alerts from vendored English weekly reports since 2024. Price $0.03 USDC. POST /api/v1/product-safety/eu-safety-gate-alert. An unpaid call returns the x402 payment terms and does not run.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "product-safety_eu-safety-gate-alert"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoto, string. Optional.
fromNofrom, string. Optional.
brandNobrand, string, length 1 to 120. Optional.
levelNolevel, string, one of Serious risk, Other risk levels, Other types of alerts. Optional.
limitNolimit, integer, from 1 to 100. Required.
queryNoquery, string, length 1 to 120. Optional.
barcodeNobarcode, string, length 1 to 40. Optional.
categoryNocategory, string, length 1 to 120. Optional.
riskTypeNoriskType, string, length 1 to 120. Optional.
notifyingCountryNonotifyingCountry, string, length 1 to 80. Optional.

Output Schema

NameRequiredDescriptionDefault
countNocount. Number.
alertsNoalerts. Array.
sourcesNosources. Array.
limitationsNolimitations. Array.
snapshotDateNosnapshotDate. String.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds genuinely non-structured behavior: $0.03 USDC cost, POST transport, and the fact that an unpaid invocation short-circuits into returning x402 payment terms rather than executing. It does not mention result volume or pagination behavior, which keeps it from 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences, front-loaded with the resource and scope, then the cost/transport, then the failure mode. Every sentence carries information an agent needs and there is no filler.

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?

An output schema exists, so return-value description is unnecessary, and the payment/execution model is disclosed. What remains thin is how the ten optional filters combine in practice and the fact that 'limit' is marked Required in the schema despite zero required parameters, a discrepancy the description does not clarify.

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% with 10 documented properties, so the schema already carries parameter meaning and the baseline of 3 applies. The description contributes nothing about filter semantics, such as whether 'query' is free-text across product names or how 'level' interacts with 'riskType', so it adds no value beyond the schema.

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 (Search) plus a precisely bounded resource: EU Safety Gate (RAPEX) non-food product alerts, restricted to vendored English weekly reports since 2024. The named source and data scope alone separate it from the sibling recall tools (CPSC, Canada, USDA) without needing to name them.

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?

Usage is only implied by the verb 'Search' plus the source scope; there is no explicit statement of when to pick this over the sibling recall search tools, nor any exclusion criteria. The payment note ('An unpaid call returns the x402 payment terms and does not run') is a useful operating prerequisite but is not selection 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.

Resources