Skip to main content
Glama
jagoff

MEMO MCP Server

by jagoff
OverviewSchemaSourceRelated ServersScoreDiscussionsAdmin
Python
Local

memo_focus_clear

Idempotent

Clears the active focus for a specified project, resetting its attention state. Returns 'cleared': false when no focus is set to confirm the action.

Instructions

Clear a project's current focus.

Idempotent: returns {'cleared': false} when no focus was set.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
projectYesProject tag whose focus should be cleared.
actor_idNoIdentifier of the agent clearing the focus (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 agent clearing the focus (journaled)."
    • addedInput schema / properties / project / description
      Added value: +"Project tag whose focus should be cleared."
  2. Addedv4.4.4

TDQS

A4/5.0
Behavior4/5

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

Adds value beyond annotations by stating idempotency and return behavior when no focus was set, though annotations already cover idempotency.

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 sentences, no redundant information, action front-loaded.

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?

Adequate for a simple tool with full schema, annotations, and output schema; could add more context about prerequisites.

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%, description adds no extra meaning beyond schema; baseline 3.

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 'Clear a project's current focus' uses a specific verb and resource, clearly distinguishing from sibling tools like memo_focus_set.

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 this tool versus alternatives; usage is implied but not stated.

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