Skip to main content
Glama
tejpalvirk

Project MCP Server

by tejpalvirk

loadcontext

Retrieve detailed context about project entities, including tasks, milestones, team members, and resources to analyze dependencies, progress, and resource allocation for informed project management decisions.

Instructions

A powerful tool for retrieving detailed contextual information about project entities, providing rich insights tailored to each entity type in the project management domain.

When to use this tool:

  • Retrieving comprehensive information about projects, tasks, milestones, and team members

  • Exploring task dependencies and critical path information

  • Examining milestone progress and completion status

  • Reviewing team member assignments and workload

  • Analyzing resource allocation and availability

  • Inspecting project risks and issues

  • Preparing for project status updates and planning meetings

  • Examining project timelines and progress metrics

  • Getting a holistic view of project status and health

  • Understanding relationships between project entities

  • Viewing entity status information (inactive, active, complete)

  • Checking priority levels for tasks and activities

  • Understanding sequential relationships between tasks

Key features:

  • Provides richly formatted, context-aware information about project management entities

  • Adapts output format based on entity type (project, task, milestone, teamMember, resource)

  • Presents both direct entity information and related elements

  • Shows project metrics, task completion rates, and milestone progress

  • Tracks entity views within the current project session

  • Formats information in a structured, readable markdown format

  • Highlights relationships between tasks, milestones, and team members

  • Presents critical path information for task dependencies

  • Shows resource utilization metrics and availability

  • Displays status information via has_status relations

  • Shows priority levels via has_priority relations

  • Presents sequential relationships through precedes relations

Parameters explained:

  1. entityName: Required - The name of the entity to retrieve context for

  • Example: "Marketing Campaign Q4", "Design Homepage", "Website Launch"

  1. entityType: Optional - The type of entity being retrieved

  • Default: "project"

  • Helps the system format the output appropriately

  • Common types include: "project", "task", "milestone", "teamMember", "resource", "status", "priority"

  1. sessionId: Optional - The current session identifier

  • Typically provided by startsession

  • Used for tracking entity views within the session

Each entity type returns specialized context information:

  • Project: Shows project status (via has_status), description, timeline, budget, goal, tasks, milestones, issues, team members, risks, and task completion rate

  • Task: Displays project affiliation, status (inactive, active, complete), priority (low, high), due date, assignee, description, critical path status, task dependencies, and task sequencing (preceding and following tasks)

  • Milestone: Shows project affiliation, status (via has_status), date, completion criteria, description, progress percentage, days remaining, required tasks, and blocking tasks

  • Team Member: Displays role, skills, availability, workload, assigned tasks, projects, upcoming deadlines, and overdue tasks

  • Resource: Shows type, project affiliation, availability, capacity, cost, usage percentage, assigned tasks, and team members using the resource

  • Status: Shows all entities assigned this status value, organized by entity type

  • Priority: Shows all entities assigned this priority value, organized by entity type

  • Other Entity Types: Shows basic entity information, observations, incoming relations, and outgoing relations

Status and Priority Information:

  • All entity displays include status information when available via has_status relations

  • Tasks and other prioritized elements show priority assignments via has_priority relations

  • Valid status values include: inactive, active, complete

  • Valid priority values include: high, low

Sequential Task Relationships:

  • Task displays show preceding and following tasks through precedes relations

  • Sequential relationships are visualized to show workflow between tasks

  • Tasks display their position in the overall project workflow

  • Critical path information highlights essential task sequences

Return information:

  • Formatted markdown text with hierarchical structure

  • Sections adapted to the specific entity type

  • Related entities shown with their relationships

  • Progress metrics and completion statistics where applicable

  • Status and priority information prominently displayed

  • Sequential relationships clearly indicated

  • Error messages if the entity doesn't exist or can't be retrieved

You should:

  • Specify the exact entity name for accurate retrieval

  • Provide the entity type when possible for optimally formatted results

  • Start with project entities to get a high-level overview

  • Examine task context to understand dependencies and critical path

  • Review milestone context to assess progress towards key deliverables

  • Use team member context to evaluate workload and assignments

  • Explore resource context to understand allocation and availability

  • Check status entities to see all project elements at the same stage

  • Review priority entities to identify critical project tasks

  • Explore sequential relationships to understand task workflows

  • After retrieving context, follow up on specific entities of interest

  • Use in conjunction with startsession to maintain session tracking

  • Remember that this tool only retrieves existing information; use buildcontext to add new entities

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
entityNameYes
entityTypeNo
sessionIdNo
Behavior4/5

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

With no annotations provided, the description carries full burden and delivers comprehensive behavioral disclosure. It explains output format ('formatted markdown text with hierarchical structure'), session tracking behavior, error handling ('Error messages if the entity doesn't exist'), and detailed return information for each entity type. The only minor gap is lack of explicit rate limit or performance characteristics.

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

Conciseness3/5

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

While well-structured with clear sections, the description is excessively long (over 700 words) with repetitive information. Multiple sections cover similar ground (entity type details appear in both 'Key features' and 'Each entity type returns' sections). The core purpose could be communicated more efficiently without sacrificing clarity.

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 3 parameters with 0% schema coverage, no annotations, and no output schema, the description provides exceptional completeness. It covers all parameters thoroughly, explains behavioral characteristics, details output format and content for each entity type, provides usage scenarios, and contrasts with sibling tools. Nothing essential appears missing for this retrieval tool.

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

Parameters5/5

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

With 0% schema description coverage, the description fully compensates with a detailed 'Parameters explained' section. It provides clear explanations for all 3 parameters including purpose, examples, defaults, and practical usage guidance. The entityType parameter explanation includes a comprehensive list of valid values and their implications for output formatting.

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 'retrieving detailed contextual information about project entities' with specific entity types (projects, tasks, milestones, team members, resources). It distinguishes from sibling tools by explicitly contrasting with 'buildcontext' (for adding new entities) and 'deletecontext' (for removal), establishing clear functional boundaries.

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 extensive explicit guidance with a dedicated 'When to use this tool' section listing 13 specific scenarios, plus a 'You should' section with 14 actionable recommendations. It clearly distinguishes when to use this tool ('only retrieves existing information') versus alternatives like 'buildcontext' (for adding new entities) and mentions integration with 'startsession' for session tracking.

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