Skip to main content
Glama

project_context

Retrieves a project's starting context—CONTEXT.md, MEMORY.md, memory files, and chat list—so agents can quickly understand and enter the project.

Instructions

Стартовый контекст проекта: CONTEXT.md, MEMORY.md и файлы памяти плюс список чатов. Самый дешёвый способ войти в проект.

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
projectYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3/5.0
Behavior2/5

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

With no annotations at all, the description carries the full behavioral burden. It discloses the payload contents and a cost hint ('cheapest'), but says nothing about read-only-ness, permissions/auth, response size, pagination, or what happens when the project is unknown — all material for a tool that pulls several files at once.

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?

Two short sentences, front-loaded with the resource inventory followed by the value proposition — no filler. Minor deduction because 'файлы памяти' is vague next to the explicitly named CONTEXT.md/MEMORY.md.

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?

Listing the returned artifacts partially compensates for the absent output schema, and the low parameter count keeps the tool simple. Still, with no annotations and an undocumented required parameter, an agent cannot fully predict the identifier format or the cost/behavior of the call.

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 0% and the single required parameter 'project' is never mentioned in the description. The agent gets no hint whether it expects a project name, slug, ID, or path, so the description adds no meaning beyond the bare schema.

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 names the concrete resources returned — CONTEXT.md, MEMORY.md, memory files, and a chat list — so an agent knows this is an aggregate project-bootstrap read. It is clear about what it does, though it never uses a verb like 'returns'/'loads' and does not explicitly contrast itself with knowledge_read or knowledge_projects.

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?

'Самый дешёвый способ войти в проект' implies this should be called first when entering an unfamiliar project, which is genuine ordering guidance. However, no alternative is named and no when-not condition (e.g. project already loaded, or need a specific file instead) is stated.

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