Skip to main content
Glama

Get Project Context

get_project_context
Read-onlyIdempotent

Retrieve a structured project context pack with memory items, recent activity, and durable context. Filter by bucket, team, or custom query to focus results.

Instructions

    Assemble a structured project context pack for the given project.

    Args:
        project_id: Project identifier (the project scope).
        bucket: Bucket filter (default "%" for all buckets).
        team_id: Optional team focus.
        max_items: Maximum context items.
        max_tokens: Maximum rendered tokens.
        include_durable_context: Whether to include long-lived durable context.
        durable_query: Optional query to focus durable context.
        recent_hours: Hours of recent activity to include.
        output_json: Return the full JSON pack instead of a text summary.
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bucketNoMemory bucket or namespace to read from or write to; use % only for tools that support wildcard reads.%
team_idNoOptional team/workspace identifier for team-scoped memory access.
agent_idNoOptional client-supplied agent label for memory attribution.
max_itemsNoMaximum number of memory items to include.
max_tokensNoApproximate maximum response size.
project_idYesInput value for the Get Project Context tool.
output_jsonNoReturn a machine-readable JSON response instead of a human-readable summary.
recent_hoursNoInput value for the Get Project Context tool.
durable_queryNoInput value for the Get Project Context tool.
agent_instance_idNoOptional stable, non-secret agent instance ID for per-client attribution.
include_durable_contextNoInput value for the Get Project Context tool.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

Annotations already indicate read-only, non-destructive, idempotent behavior. The description adds that the tool can return a full JSON pack instead of a text summary, and mentions assembling context, which is consistent and adds value.

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

Conciseness3/5

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

The description includes a one-line summary followed by a parameter list, which is structured but somewhat verbose due to 11 parameters. It could be more concise.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity (11 parameters, output schema exists), the description covers purpose, parameters, and output format but lacks usage guidelines, behavioral expectations, and examples, making it adequate but not complete.

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 description coverage is 100%, but the description merely repeats parameter names and defaults without adding meaning. Many schema descriptions are generic, and the description does not improve them.

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 clearly states it assembles a structured project context pack for a given project. It distinguishes the tool's action but does not explicitly differentiate from sibling tools like recall_context.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives or when not to use it. It only lists parameters without context.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/yonro/memory-os-cli'

If you have feedback or need assistance with the MCP directory API, please join our Discord server