Skip to main content
Glama

get_project_context

Retrieve the active project workspace context briefing for the authenticated user, including project metadata, pinned AI Context Notes (userNotes), and workspace summary. Call this at the start of a session to understand the active project's conventions and notes.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_project_context"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior3/5

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

With no annotations, the description must carry the full behavioral burden. It discloses the read-only nature ('Retrieve'), the scope (authenticated user's active project), and the returned contents, but says nothing about what happens when no active project is set, whether notes are truncated, or any authorization prerequisites beyond 'authenticated user'.

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?

Two sentences, front-loaded with the payload contents and followed by the usage cue. No redundant restatement of the name and nothing extraneous.

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?

No output schema exists, so the description responsibly enumerates what is returned. The missing piece is the edge case of an unset or ambiguous active project, which matters for a context-priming call an agent makes at session start.

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 tool takes zero parameters, so there is no schema semantics to compensate for; baseline is 4. The description usefully clarifies that scope comes implicitly from the authenticated user's active project rather than from an explicit selector.

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 ('Retrieve') and resource ('active project workspace context briefing') and enumerates the payload: project metadata, pinned AI Context Notes (userNotes), and workspace summary. That is enough for an agent to distinguish it from list_projects or get_state, though it never names a sibling as an alternative.

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?

'Call this at the start of a session' gives an explicit trigger condition for invocation. There is no when-not guidance or named alternative for fetching notes for a non-active project, which keeps it short of a 5.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources