Skip to main content
Glama

project_context

Fetch a project's current decisions, pending tasks, and completed work in a compact index; retrieve full memory text by ID when needed.

Instructions

Fetch the latest context of a project: decisions, pending tasks, completed work. Default mode "index" returns one compact line per memory with its id (cheap on tokens); call get_memory with the ids you need for full text. Use mode "full" to get everything at once.

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_context"
  }
}

Input Schema

NameRequiredDescriptionDefault
modeNo"index" = one line per memory with id; "full" = complete textindex
limitNoMaximum number of memories
projectYesProject path or name

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.16.1
    • addedInput schema / properties / limit / description
      Added value: +"Maximum number of memories"
    • addedInput schema / properties / mode / description
      Added value: +"\"index\" = one line per memory with id; \"full\" = complete text"
  2. First observed

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does disclose the key behavioral trait: "index" is cheap on tokens while "full" returns complete text, which shapes token-budget decisions. It does not mention permissions, error behavior, or what happens when a project has no memories, so it falls short of fully covering a mutation-free but opaque read.

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?

Three sentences, front-loaded with what is fetched and the token-cost tradeoff before the follow-up workflow. Slight redundancy with the schema's enum descriptions costs it a point but nothing is padding.

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?

There is no output schema, and the description compensates by explaining the shape of results (one compact line per memory with its id versus complete text). The limit parameter's effect on results is left to the schema, which is a minor gap for a three-parameter read tool.

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 mode, limit, and project are already documented in the schema; baseline is 3. The description reinforces mode semantics but adds no syntax or format detail beyond the enum descriptions, and the limit parameter is not discussed at all.

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?

States a specific verb and resource ("Fetch the latest context of a project") and enumerates the content returned: decisions, pending tasks, completed work. It also distinguishes the two operating modes and names get_memory as the companion tool, so an agent can tell what this does without opening the schema.

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?

Gives explicit when-to-use guidance: default to "index" for cheap id-level scanning, then call get_memory with the needed ids, or use "full" to retrieve everything at once. Both the recommended path and the alternative are named with the condition that selects each.

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