Skip to main content
Glama

Recall Kitchen

by io.github.adamdecaf

list_recall_notifications

Read-onlyIdempotent

List recall notifications for this API key. unread defaults to true (unread only); pass false for all. Empty for new accounts until a new matching recall is published; not a backfill of check_tracked_products. message is a short plain-text summary. Requires an API key.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNonumber of notifications to return
offsetNonumber of notifications to skip
unreadNoif true, only unread notifications; if false, include read. Default: true (unread only)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
offsetYes
messageNo
nextOffsetNo
notificationsYes

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint as safe. The description adds useful behavioral context: the unread default, empty-for-new-accounts behavior, the non-backfill relationship to check_tracked_products, and that message is a short plain-text summary. No contradiction exists.

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?

Four short sentences deliver all key information with no filler. The core action is front-loaded, and each subsequent sentence adds either parameter behavior, result expectations, or output format context.

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?

Given the simple tool shape, complete schema coverage, output schema presence, and safe annotations, the description provides everything an agent needs for a correct call: default filter, result emptiness, distinction from a sibling tool, message format, and auth requirement.

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 the schema already documents all three parameters. The description adds minor clarification about the unread default and the response's message field, but limit and offset semantics remain fully handled by the schema. Baseline 3 is appropriate.

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?

The description states a clear verb and resource: 'List recall notifications for this API key.' It also distinguishes itself from the sibling check_tracked_products by explicitly saying it is 'not a backfill' of that tool, so an agent can identify its unique purpose.

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?

The description explains how to get all notifications versus unread only, and sets expectations for empty results on new accounts. It also names check_tracked_products as a related but different operation. It does not enumerate every alternative sibling tool, but the guidance is sufficient for the common decision.

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

All Recall Kitchen toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.1/5.0
Disambiguation4/5

Most tools have clear, distinct resource-action boundaries (inventory vs. watch patterns vs. notifications vs. search). The search tools overlap somewhat—especially search_product_recalls_by_upc, search_product_recalls_from_image, and search_recalls_by_identifier—but their input types and intent are described well enough to avoid major confusion.

Naming Consistency4/5

The overwhelming majority follow a predictable verb_noun snake_case pattern (add_inventory_product, list_watch_patterns, revoke_api_key). Minor deviations like signup, list_inventory, and search_recalls_by_identifier (instead of search_product_recalls_by_identifier) keep it from being perfectly consistent.

Tool Count4/5

With 19 tools, the server is slightly on the heavier side, but the count is justified by covering several distinct areas: account/key management, inventory, watch patterns, recall search, and notifications. Each tool appears to serve a real purpose, though a few search variants could arguably be consolidated.

Completeness4/5

The set covers the core lifecycle well: signup, key management, inventory and watch pattern add/list/remove, multiple recall search paths, recall detail lookup, and notification read state. Minor gaps exist, such as no update operation for inventory items or watch patterns and no bulk notification actions, but agents can work around these.

Resources