Skip to main content
Glama

get_summary

Read the project memory summary before answering project questions to get a distilled, authoritative status and verify recorded work without rescanning source files.

Instructions

Read the project memory summary.

MANDATORY: call this BEFORE answering ANY question about the project.

Do NOT answer from conversation history alone.
Do NOT re-scan source files (package.json, README, src/) to understand
the project — `summary.md` is the distilled authoritative source and
stays bounded as the project ages (a few hundred tokens on a young
project, a few thousand on an aged one), far less than re-deriving it.

Your prior assumptions about this project may be stale. Call this
cheaply at session start (and again before ending) to verify your
work is recorded.

Read-only; does not modify memory or trigger event logging.

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": "get_summary"
  }
}

Input Schema

NameRequiredDescriptionDefault
projectNoWhich project this call is about — a registered id, alias, or absolute path (e.g. 'ossdrop'). Omit it when the server was started for a single repo, or when an active project is set with `pjm project use`. Call list_projects to see the registered names.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.3.2
    • addedInput schema / properties / project
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "description": "Which project this call is about — a registered id, alias, or absolute path (e.g. 'ossdrop'). Omit it when the server was started for a single repo, or when an active project is set with `pjm project use`. Call list_projects to see the registered names.",
      +  "title": "Project"
      +}
  2. First observedv0.1.1

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations present, the description carries the full burden, and it delivers the key traits: read-only, does not modify memory, does not trigger event logging, and returns a size-bounded payload that grows only modestly with project age. It omits error/empty behavior (e.g. what happens for an unregistered project) and any latency or rate context.

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?

The purpose is front-loaded in the first line and the guardrails are short and scannable. There is mild redundancy — the staleness point and the 'don't re-derive' point are restated across the middle and final paragraphs — but the emphasis is defensible for a mandatory-call tool.

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?

An output schema exists, so return shape need not be explained, and the one optional parameter is fully covered by the schema. What remains missing is how this tool relates to sibling memory-read tools (map, plan, instructions) and what it returns when no summary exists yet.

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 description coverage is 100% and the single `project` parameter is fully documented in the schema, including alias/path forms and when to omit it. The description adds nothing about the parameter, so the baseline of 3 applies.

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?

The description gives a specific verb and resource ('Read the project memory summary') and characterizes the resource as a bounded, distilled `summary.md`. It does not, however, distinguish itself from close siblings like get_project_map, get_plan, or get_instructions, which an agent could reasonably confuse with a 'summary' read.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It is unusually explicit about when to call: before answering any project question, at session start, and again before ending. It also names what to do instead of this tool ('Do NOT re-scan source files') and warns against the wrong alternative ('Do NOT answer from conversation history alone').

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