Skip to main content
Glama

safepulse

Retrieve real-time safety recalls and alerts for consumer products, vehicles, food, and home items worldwide. Get brand safety scores and EU/global reports.

Instructions

SafePulse: SafePulse — product safety intelligence: CPSC, FDA, USDA FSIS, NHTSA recalls; EU RAPEX; home safety scores; child/vehicle safety ratings; food safety alerts worldwide.

Coverage: Global

Endpoints: • recall ($0.10): Active recall dashboard • product ($0.10): Consumer product safety • vehicle ($0.10): Vehicle safety • food ($0.10): Food and drug recall • home ($0.10): Home safety hazards • child ($0.10): Child product safety • score ($0.10): Brand safety score • eu ($0.10): EU Safety Gate alerts • global ($0.10): Global safety alerts

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actionYesWhich endpoint to call. Options: recall | product | vehicle | food | home | child | score | eu | global
langNolang
categoryNoFilter by recall category
productNoproduct
makeNomake
modelNomodel
yearNoyear
typeNotype
roomNokitchen | bedroom | bathroom | garage | nursery
age_groupNoinfant | toddler | preschool | school-age
brandNobrand
product_typeNoproduct_type
countryNoFilter by EU country (e.g. Germany, France, Spain)
regionNocanada | australia | uk | who | global
Behavior2/5

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

No annotations are provided, so the description carries full burden. It mentions cost per endpoint ($0.10) but does not disclose side effects, data freshness, authentication requirements, or what happens on error. Behavioral traits beyond cost are missing.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

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

The description is structured but verbose, listing all endpoints with costs inline. It could be more concise by summarizing endpoint categories. Some redundancy (repeating 'SafePulse'). Adequate but wordy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With 14 parameters and no output schema, the description does not explain return value structure, pagination, or how parameters interact. It lacks completeness for a complex tool with many optional filters.

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% with descriptions for all 14 parameters. However, many descriptions are just parameter names (e.g., 'product', 'make') adding little meaning. The action parameter has a good enum. Overall, the description adds minimal value beyond the schema.

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 clearly states the tool provides product safety intelligence covering multiple agencies (CPSC, FDA, etc.) and categories. However, it lacks a single concise verb phrase like 'retrieve safety recalls and ratings' and is more of a catalog listing endpoints.

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

Usage Guidelines2/5

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

No explicit guidance on when to use this tool versus siblings. The description only lists endpoints without comparing to other pulse tools. The context of sibling tools is diverse (e.g., alphapulse, cryptopulse), but the description does not help differentiate usage scenarios.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/GTCC777/pulsenetwork-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server