Skip to main content
Glama
tejpalvirk

Project MCP Server

by tejpalvirk

startsession

Initiate a project management session to review active projects, prioritize high-impact tasks, track upcoming milestones, assess project health, and identify risks. Streamline workflows by sequencing tasks and maintaining continuity between sessions.

Instructions

A comprehensive tool for initializing a new project management session, providing structured information about ongoing projects, tasks, deadlines, and overall project health.

When to use this tool:

  • Beginning a new project management session

  • Getting oriented to your current project portfolio status

  • Planning which projects or tasks to focus on in the current work session

  • Reviewing recent project activity and progress

  • Checking upcoming deadlines for tasks and milestones

  • Assessing the health of active projects

  • Identifying high-priority tasks requiring attention

  • Reviewing project risks that need mitigation

  • Establishing context before diving into specific project work

  • Creating a structured record of your project management activity

  • Tracking the status of various project entities

  • Managing sequential task dependencies

Key features:

  • Generates a unique session identifier for tracking project management activities

  • Retrieves and displays your most recent project management sessions

  • Shows active projects you're currently managing with status information

  • Highlights high-priority tasks requiring attention

  • Lists upcoming milestones with progress metrics

  • Provides project health summaries with status indicators

  • Identifies top project risks requiring mitigation

  • Formats information in a structured, easy-to-read format

  • Integrates with the loadcontext tool for deeper exploration

  • Maintains continuity between project management sessions

  • Displays status information through has_status relations

  • Shows priority assignments through has_priority relations

  • Presents task sequencing through precedes relations

Parameters explained: No parameters required - the tool automatically retrieves all relevant context.

Return information:

  • Session ID: A unique identifier for this project management session

  • Recent Project Management Sessions: Up to 3 most recent sessions with:

    • Date

    • Project focus

    • Session summary (truncated for readability)

  • Active Projects: List of current projects with:

    • Project name

    • Current status (via has_status relation)

    • Deadline information

  • High-Priority Tasks: Up to 10 highest priority tasks with:

    • Task name

    • Associated project

    • Status (inactive, active, complete)

    • Priority (high via has_priority relation)

    • Assignee

  • Upcoming Milestones: Up to 8 nearest milestones with:

    • Milestone name

    • Associated project

    • Due date

    • Completion percentage

    • Status (via has_status relation)

  • Project Health Summary: Status of active projects with:

    • Project name

    • Health status indicator

    • Health score

    • Issue count

    • Risk count

  • Top Project Risks: Up to 5 highest severity risks with:

    • Risk name

    • Associated project

    • Severity level

    • Impact assessment

  • Next Sequence Tasks: Up to 5 tasks ready to be worked on next based on sequential dependencies:

    • Task name

    • Associated project

    • Status (via has_status relation)

    • Prerequisites completion status

Status and Priority Information:

  • Project and task status is retrieved through has_status relations

  • Valid status values include: inactive, active, complete

  • Task priority is retrieved through has_priority relations

  • Valid priority values include: high, low

  • This information helps you prioritize your project management activities

Sequential Task Management:

  • Tasks are presented in their logical sequence based on precedes relations

  • Prerequisite tasks must be completed before dependent tasks can begin

  • The sequential view helps identify the next logical actions in project workflows

  • Critical path tasks are highlighted to show dependencies affecting project timelines

Session Workflow:

  1. Start a project management session with startsession

  2. Review the provided context to decide what to focus on

  3. Use loadcontext to retrieve detailed information about specific projects

  4. Conduct your project management work, adding new elements with buildcontext as needed

  5. End the session when work is complete

  6. Record progress, decisions, and next steps

You should:

  • Begin each focused project management period with startsession

  • Review recent sessions to maintain continuity in your work

  • Prioritize work based on high-priority tasks and upcoming milestones

  • Address projects with poor health indicators

  • Mitigate high-severity risks promptly

  • Focus on tasks that are next in sequence based on precedes relations

  • Complete prerequisite tasks to unblock dependent tasks

  • Check entity status to identify active work items

  • Use the session ID when using other tools to maintain session tracking

  • Establish a regular cadence of project management sessions

  • Use the structured overview to make deliberate choices about where to focus your effort

  • Consider creating or updating project entities after reviewing the current state

  • Follow up on projects with approaching deadlines

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior4/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It effectively describes behavioral traits such as generating a unique session ID, retrieving recent sessions (up to 3), listing active projects, highlighting high-priority tasks (up to 10), and formatting information in a structured way. However, it lacks details on potential errors, performance characteristics, or rate limits, which slightly limits transparency.

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

Conciseness2/5

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

The description is excessively long and verbose, with redundant sections (e.g., repeating status/priority information and workflow advice). While it is front-loaded with purpose and usage, many sentences (like detailed lists of return fields and extensive workflow instructions) do not earn their place, making it overly detailed and less concise than ideal for a tool description.

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?

Given the tool's complexity (project management session initialization) and the absence of annotations and output schema, the description provides comprehensive context. It details return information, status/priority handling, sequential task management, session workflow, and usage recommendations, making it complete enough for an agent to understand and invoke the tool effectively without structured output data.

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 input schema has 0 parameters with 100% coverage, so the baseline is 4. The description adds value by explicitly stating 'No parameters required - the tool automatically retrieves all relevant context,' which clarifies the parameterless nature and the tool's automatic context retrieval behavior, going beyond what the schema alone provides.

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?

The description clearly states the tool's purpose as 'initializing a new project management session' and 'providing structured information about ongoing projects, tasks, deadlines, and overall project health.' It distinguishes itself from siblings like 'loadcontext' (for deeper exploration) and 'buildcontext' (for adding new elements), making the verb+resource+scope specific and differentiated.

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

Usage Guidelines5/5

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

The description provides explicit guidance on when to use this tool, including a dedicated 'When to use this tool' section with 12 specific scenarios (e.g., 'Beginning a new project management session,' 'Getting oriented to your current project portfolio status'). It also contrasts with alternatives by mentioning integration with 'loadcontext' for deeper exploration and outlines a session workflow that positions 'startsession' as the initial step, clearly differentiating it from sibling 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

Related 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/tejpalvirk/project'

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