Skip to main content
Glama

project_get

Reads the project task tree, ready/waiting status, active sibling chats and files, upstream handoff notes and pinned notes, optionally focused on one task, so you can resume multi-day engineering work.

Instructions

Read the project task tree, ready/waiting status, active sibling chats/files, upstream handoff_notes, and pinned 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": "project_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
task_idNoOptional focus task ID to include upstream handoff_notes.
project_idNoOptional project ID (auto-resolved when omitted).
include_notesNoInclude project notes (default true).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the full burden; "Read" implies a safe non-mutating operation and the enumerated outputs give a decent picture of what comes back. It omits permission requirements, output volume, and whether records are filtered or truncated, which matters for a potentially large task tree.

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?

One front-loaded sentence with the verb first and no filler; every listed item is a distinct piece of returned state. The flat comma list is dense and gives no hierarchy between core tree data and auxiliary notes, but nothing is wasteful.

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?

Covers what is returned for a zero-required-parameter read tool with no output schema, which is the main thing an agent needs. It does not describe the shape of the task tree or what happens when project_id cannot be auto-resolved, leaving some ambiguity for a multi-resource read.

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

Parameters3/5

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

Schema coverage is 100%, so the schema already documents all three optional parameters including auto-resolution of project_id and the include_notes default. The description only indirectly echoes task_id's effect by naming upstream handoff_notes, adding marginal meaning beyond structured fields.

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?

Uses a specific verb ("Read") plus a concrete set of resources: project task tree, ready/waiting status, sibling chats/files, handoff_notes, pinned notes. An agent can tell this is a state-read tool rather than a mutation, though it never explicitly contrasts itself with siblings like project_list or task_plan.

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?

Usage is only implied by the enumerated payload — an agent infers it is for loading project context before acting. There is no explicit when-to-use, no when-not, and no mention of project_list or task_plan as alternatives for coarser or planning-oriented reads.

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