Skip to main content
Glama

MemBrowse

Memory history

get_memory_history
Read-only

List a target's commits, newest first, with each memory region's used size and the change that commit made. Use it to see how memory evolved and to find the commits that grew it (the largest positive 'delta'); page back with 'offset'.

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": {
      "project": "<project>",
      "target": "<target>"
    },
    "name": "get_memory_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
refNoWhere to start: a full commit SHA, a SHA prefix (7+ characters), or a branch or tag name. Default: the head of the default branch.
limitNoCommits per page (default 30, max 200).
offsetNoCommits to skip, for paging (default 0).
regionNoOnly this memory region, e.g. FLASH or RAM.
targetYesTarget name (see list_targets).
projectYesThe project: a public project's GitHub 'owner/repo' (no API key needed), or, with an API key, a project id or name from list_projects.
only_changedNoSkip commits whose build was identical to the previous one (default true).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds useful behavior beyond that: results are ordered newest first and paging is done via 'offset'. It does not discuss the default filtering behavior (only_changed) or any rate/limit behavior, leaving that to the schema.

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

Conciseness4/5

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

Two sentences, front-loaded with what is returned before the use case, with zero filler. Slightly dense with quoting of 'delta' and 'offset', but nothing is wasted.

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?

With no output schema, the description carries the burden of describing returns, and it does so (commits, per-region used size, per-commit change). It leaves minor ambiguity about units of 'used size' and the sign convention of 'delta', but overall it is sufficient to call the tool correctly.

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%, so every parameter including ref, limit, offset, region and only_changed is already documented in structured data; baseline 3 applies. The description only reinforces 'offset' for paging and introduces the 'delta' concept, adding little that the schema does not already carry.

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 names a specific verb and resource ('List a target's commits') and enumerates the payload ('each memory region's used size and the change that commit made'), so the agent knows exactly what comes back. That payload description also separates it in effect from siblings like get_commit_summary or get_metric_history, which would not return per-region memory sizes.

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?

It gives a concrete when-to-use: 'see how memory evolved' and 'find the commits that grew it (the largest positive delta)'. That is clear context for selection, but no explicit exclusions or named alternatives are given, so it stops short of a full when/when-not statement.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources