Skip to main content
Glama
jagoff

MEMO MCP Server

by jagoff
OverviewSchemaSourceRelated ServersScoreDiscussionsAdmin
Python
Local

memo_attention_ack

Idempotent

Acknowledge an attention item to stop it from being surfaced again. Use this action to dismiss alert reminders once they are no longer relevant.

Instructions

Acknowledge an attention item so it stops being surfaced.

Idempotent: returns {'acknowledged': false} when the id is unknown or already acknowledged; true only on the first acknowledgement.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesId of the attention item to acknowledge.
actor_idNoIdentifier of the acknowledging agent (journaled).memo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

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

  1. Changed2 schema fields changedv4.4.6
    • addedInput schema / properties / actor_id / description
      Added value: +"Identifier of the acknowledging agent (journaled)."
    • addedInput schema / properties / id / description
      Added value: +"Id of the attention item to acknowledge."
  2. Addedv4.4.4

TDQS

A4/5.0
Behavior4/5

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

Extends beyond the idempotentHint annotation by detailing the exact return values for known/unknown/already acknowledged cases. This helps the agent understand the tool's exact behavior.

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 concise sentences, front-loaded with the main purpose, and no wasted words. Efficient and clear.

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?

Comprehensive enough for a simple idempotent acknowledgment tool with output schema and annotations. Slightly lacking in connecting 'attention item' to broader context, but still good.

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 covers both parameters with 100% description coverage. The description adds no additional parameter semantics beyond the schema, so a baseline score of 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 specific verb 'Acknowledge' and resource 'attention item', and explains the effect 'stops being surfaced'. It is clear and distinguishable from sibling tools.

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?

No explicit guidance on when to use or alternatives are provided. The purpose is clear but an agent might benefit from knowing this is for dismissing attention items rather than other actions.

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/jagoff/memo'

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