Skip to main content
Glama

DeNasty Memory

Recall project memory

recall
Read-only

Returns what DeNasty remembers about a project (decisions, conventions, context, open tasks, notes), newest first. Optional text query and kind filter. Omit project to search across all projects.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "recall"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindNo
limitNo
queryNoWords to search for
projectNoProject or repository name, e.g. my-app

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered; the description adds real value beyond that with result ordering (newest first), the categories of content returned, and the cross-project scoping rule when project is omitted. It stops short of describing volume behavior — no default for limit, no statement about truncation when many memories match.

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?

Three short sentences, front-loaded with the return content and ending with the most actionable rule (omit project to search broadly). Nothing is padded or repeated from the schema.

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?

For a read-only, zero-required-parameter retrieval tool with no output schema, this covers what the agent needs to select and call it: content scope, ordering, filters, and cross-project behavior. The only material gap is the limit parameter's default and interaction with result ordering.

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 50%: project and query are documented in the schema, while kind and limit are not. The description compensates partially by explaining the semantics of omitting project and by treating query as free-text filtering, but limit is never mentioned (no default, no cap rationale) and kind's filter behavior is only implied by the parenthetical list.

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

Purpose4/5

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

"Returns what DeNasty remembers about a project" gives a specific verb and resource, and the parenthetical enumerates the record kinds (decisions, conventions, context, open tasks, notes) plus ordering. It reads clearly as the read/retrieval counterpart to remember/forget, though it never names those siblings to sharpen the contrast.

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?

It implies usage by explaining that query and kind are optional filters and that omitting project widens the search to all projects — useful context for how to call it. But there is no explicit guidance on when to prefer this over project_brief, list_projects, or my_preferences, so the agent must infer the boundary.

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