Skip to main content
Glama
SVerITG

Metis

by SVerITG
OverviewSchemaRelated ServersScoreDiscussions
Python
Local

Metis — Load Project Context

load_project_context

Loads a project's context document, recent session history, and next step into a structured brief to provide full background at the start of a work session.

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. "hat-dashboard", "article-1").

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Tool Definition Quality

A4.3/5.0
Behavior3/5

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

With no annotations, the description carries full burden. It states the tool returns context_doc, session history, and next step. However, it does not disclose whether the tool is read-only, requires permissions, or has side effects. The description is truthful but lacks depth regarding behavioral traits.

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

Conciseness5/5

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

The description is very concise: two sentences of purpose and one for the parameter. Every sentence adds value, and critical info is front-loaded. No wasted words.

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

Completeness5/5

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

For a simple tool with one parameter and an output schema, the description covers all necessary aspects: purpose, return values, usage timing, and parameter details. It is complete for its complexity.

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?

The description adds a meaningful docstring for the single parameter, including a format example. Schema coverage is 0%, so the description compensates well by explaining the parameter's purpose and expected value.

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?

Description clearly states the tool loads the full context block for a project, specifying the verb 'load', the resource 'project context', and the purpose 'ready to paste into Claude'. It distinguishes from sibling context tools by focusing on project-specific context with a structured brief.

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?

Explicitly recommends use at the start of any work session on a specific project. Provides clear context but does not mention when not to use or list alternative tools.

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/SVerITG/Metis'

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