Skip to main content
Glama

get_project_board

Retrieves a compact project state card with goals, constraints, decisions, tasks, alerts, and recent activity to provide situational awareness at the start of a session.

Instructions

Retrieves the living Tier 1 Project State Card (< 500 tokens). Call this tool at the beginning of a session or whenever you need situational awareness of the project. It synchronizes recent turns from local client transcripts (Antigravity and Codex) and compiles a high-density, deterministic markdown card. Contains:

  • 🎯 Project Goal & Scope

  • 🔒 Binding Invariants (lossless constraints, exact PRAGMAs, paths, versions)

  • 🏛️ Active Architectural Decisions (ADR IDs, titles, rationale, author, date)

  • 📋 Active Tasks & Handoff Baton (in-progress items with @owner, pending tasks)

  • ⚠️ Attention Required (health alerts: unowned tasks, unverified completions)

  • 🔄 Recent Ambient Activity (recent client messages, budget permitting) Args: target_tokens: Desired token budget ceiling for the briefing card (default: 450). Enforced accurately via the BPE tokenizer.

Returns: str: Clean Markdown-formatted Tier 1 State Card ready to be placed directly into your context window without prompt bloat.

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_board"
  }
}

Input Schema

NameRequiredDescriptionDefault
target_tokensNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A3.9/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 substantial work: it discloses that the tool synchronizes recent turns from local client transcripts (Antigravity and Codex), that the output is deterministic markdown, and that behavior is "budget permitting." It stops short of stating whether the transcript sync mutates or persists state, what permissions are needed, or what happens on a cold cache — meaningful gaps for a tool that reads local files.

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 action and call trigger are front-loaded, and the bulleted content list is scannable. Some lines are padding, particularly the closing "ready to be placed directly into your context window without prompt bloat" and the emoji decoration, which do not change invocation behavior.

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?

For a single-optional-parameter tool with an output schema, the description is nearly complete: it explains purpose, trigger, output shape, and the token-budget mechanism. The remaining gap is the side-effect profile of the transcript synchronization, which an agent would want to know before calling it repeatedly.

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 0%, so the description must compensate, and it does explain target_tokens as a "desired token budget ceiling" enforced "accurately via the BPE tokenizer" with a default of 450. That adds real meaning over the bare integer, but it does not say what happens if the budget is exceeded or what a sensible range is.

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 ("Retrieves the living Tier 1 Project State Card") and enumerates the exact sections returned, so the agent knows what it is getting. It does not name or contrast any sibling such as get_project_summary or get_recent_context, so the differentiation burden is left to the reader.

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?

Gives an explicit trigger: "Call this tool at the beginning of a session or whenever you need situational awareness of the project." That is a clear usage context, but there is no when-not guidance and no named alternative for cases where a narrower lookup (e.g. a single turn or a summary) is preferable.

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