Skip to main content
Glama

DeNasty Memory

Project brief (Markdown)

project_brief
Read-only

Returns the project's memory as a Markdown section ready to paste into CLAUDE.md, AGENTS.md or Cursor rules.

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>"
    },
    "name": "project_brief"
  }
}

Input Schema

NameRequiredDescriptionDefault
projectYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

readOnlyHint=true and openWorldHint=false already establish that this is a safe, local read, so the description does not need to argue safety. It does add useful context that the output is a paste-ready Markdown section rather than raw records, but says nothing about failure on unknown projects, size limits, or whether memory is truncated.

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?

A single front-loaded sentence with zero wasted wording; the output format and intended destination are packed into one clause each.

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 one-parameter read tool with annotations covering the safety profile and no output schema, the description is nearly sufficient: it explains what comes back (a Markdown section) and what it is for. The remaining gap is the meaning and expected format of the 'project' argument.

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

Parameters2/5

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

Schema coverage is 0% and there is a single required 'project' parameter whose form (name, slug, or ID) is never clarified. The description does not compensate for the coverage gap at all, so an agent must guess what identifier to supply.

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?

States a specific verb and resource: 'Returns the project's memory as a Markdown section.' It also names the concrete consumer artifacts (CLAUDE.md, AGENTS.md, Cursor rules), which makes it clearly distinguishable from a search-style sibling like recall. It stops short of explicitly contrasting itself with any sibling, keeping it at 4 rather than 5.

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?

The 'ready to paste into CLAUDE.md, AGENTS.md or Cursor rules' framing implies the use case (exporting/installing project memory into an agent config), but there is no explicit when-to-use vs when-not, and no named alternative such as recall for on-demand lookups. Usage is inferable rather than stated.

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