Skip to main content
Glama

memory

Store and retrieve notes across web pages with source URLs. Use key-based actions to set, get, list, or delete persistent context during browser automation.

Instructions

Notes kept across pages, with source URL.

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": {
      "action": "<action>"
    },
    "name": "memory"
  }
}

Input Schema

NameRequiredDescriptionDefault
keyNo
valueNo
actionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

D1.8/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full burden and largely drops it. It does not disclose that set/delete/clear mutate or destroy stored data, whether memory is scoped per session/page, whether clear wipes everything, or what get/list return. Only the vague 'kept across pages' hints at persistence semantics.

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

Conciseness2/5

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

It is a single short fragment, but the brevity is under-specification rather than concision — nothing is front-loaded because there is no action statement to lead with. Every sentence 'fits' only because there is almost nothing in it.

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

Completeness1/5

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

A multi-action tool with destructive operations, zero annotation coverage, 0% parameter documentation, and no output schema needs a description that explains actions and their effects. This one provides none of that, leaving the agent to guess at semantics for delete and clear in particular.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% for three parameters, including a five-value action enum (set/get/list/delete/clear), and the description explains none of them. It never says what key and value mean, which actions require which parameters, or that action is required. The description adds no meaning whatsoever beyond the raw schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description characterizes the stored resource ('Notes kept across pages, with source URL') but never states what the tool does — there is no verb indicating read/write/list/delete. An agent cannot tell from this text that the tool is a key-value memory store driven by an action enum. It is closer to a restatement of the resource than a statement of capability.

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 when-to-use guidance, no exclusions, and no mention of how this relates to siblings such as snapshot or extract. At best 'kept across pages' hints at persistence across navigation, which implies a use case, but nothing tells the agent when to choose this over other tools.

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

Deploy Server

Other Tools