Recall Kitchen

mark_notification_read

Idempotent

Mark a recall notification as read (default) or unread. Requires an API key.

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": {
      "recall_id": "<recall_id>"
    },
    "name": "mark_notification_read"
  }
}

Input Schema

Name	Required	Description	Default
`read`	No	if true, mark read; if false, mark unread. Default true
`recall_id`	Yes	recall id from list_recall_notifications

Output Schema

Name	Required	Description	Default
`read`	Yes
`updated`	Yes
`recall_id`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedSep 6, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Beyond the annotations, the description reveals the default behavior (read), the optional unread mode, and the API-key requirement. This supplements the structured hints without contradicting them, though it does not describe response or side-effect details (covered by output schema/annotations).

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?

Two short sentences convey the operation and an auth prerequisite with zero filler. The core behavior is front-loaded and the API-key note is kept brief.

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?

For a simple two-parameter mutation with full schema coverage, idempotency and destructiveness annotations, and an output schema, this description gives the agent everything needed to invoke it correctly. No material gap remains.

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%: recall_id and read are both documented with their meanings and default. The description only restates the default behavior already present in the schema, so it adds no new parameter-level meaning.

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 starts with a specific verb and resource: 'Mark a recall notification as read (default) or unread.' This clearly differentiates it from the recall-search and inventory sibling tools, which operate on different resources.

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 context is clear: this tool updates notification read state and requires an API key. It does not explicitly name alternatives or when-not-to-use conditions, but no sibling tool performs the same notification-status mutation, so the implicit usage context is sufficient.

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

All Recall Kitchen tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.