Skip to main content
Glama

Metis — Load Project Context

load_project_context

Retrieves a project's context document, recent session history, and next step as a structured brief so Claude starts each work session with full background.

Instructions

Load the full context block for a project — ready to paste into Claude.

Returns the project's context_doc, recent session history, and next step
formatted as a structured brief. Use this at the start of any work session
on a specific project so Claude has full background.

Args:
    project_id: The project slug (e.g. "cohort-analysis", "article-1").

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_id": "<project_id>"
    },
    "name": "load_project_context"
  }
}

Input Schema

NameRequiredDescriptionDefault
project_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/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 reasonably well: 'Load' plus the itemized return contents make clear this is a non-mutating retrieval that produces a formatted brief. It does not discuss any side effects on session state, but none are implied.

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 core purpose and return contents are front-loaded in the first two sentences, then usage guidance. The Google-style 'Args:' block for a single parameter is slightly heavy for one field but not wasteful.

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?

Purpose, return contents, usage timing, and the one required parameter are all covered; an output schema exists, and the return description is a helpful bonus rather than a crutch. Only sibling differentiation is missing, which matters given the dense set of adjacent context/bootstrap tools.

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

Parameters4/5

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

Schema coverage is 0% — the schema only declares a bare string 'Project Id'. The description compensates by defining it as the project slug and giving concrete examples ('cohort-analysis', 'article-1'), which is exactly the compensating detail needed.

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 ('Load the full context block for a project') and enumerates what is returned (context_doc, recent session history, next step). It does not explicitly distinguish itself from nearby siblings like get_project_status, get_context, or session_bootstrap, so an agent must infer the difference.

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

Usage Guidelines4/5

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

'Use this at the start of any work session on a specific project so Claude has full background' gives a clear triggering condition. It stops short of naming alternatives or stating when not to use it (e.g. vs. session_bootstrap or get_project_status).

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

Deploy Server

Other Tools