Skip to main content
Glama
davidorex

Project Handoffs MCP Server

by davidorex

list_templates

Browse available templates for project handoffs, next steps, and working sessions to organize tasks and manage workflows.

Instructions

List available templates for next steps, working sessions, and handoffs

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function for the 'list_templates' tool. It returns a text content containing the JSON representation of all available HANDOFF_TEMPLATES.
    case "list_templates":
      return {
        content: [{
          type: "text",
          text: JSON.stringify(HANDOFF_TEMPLATES, null, 2)
        }]
      };
  • src/index.ts:291-298 (registration)
    Registration of the 'list_templates' tool in the ListTools response, including name, description, and empty input schema.
    {
      name: "list_templates",
      description: "List available templates for next steps, working sessions, and handoffs",
      inputSchema: {
        type: "object",
        properties: {}
      }
    },
  • The HANDOFF_TEMPLATES constant defining the schema and fields for various entity types (next_step, working_session, handoff), which is returned by the list_templates tool.
    export const HANDOFF_TEMPLATES: Record<string, EntityTemplate> = {
      next_step: {
        type: "next_step",
        description: "Defines next work to be done",
        fields: [
          {
            name: "title",
            description: "Brief title of the next step",
            required: true,
            format: "Title: ${title}"
          },
          {
            name: "description",
            description: "Detailed description of work",
            required: true,
            format: "Description: ${description}"
          },
          {
            name: "priority",
            description: "Implementation priority level",
            required: true,
            format: "Priority: ${priority}"
          },
          {
            name: "dependencies",
            description: "IDs of dependent next steps",
            required: false,
            format: "Dependencies: ${dependencies}"
          }
        ]
      },
      working_session: {
        type: "working_session",
        description: "Records AI working session details",
        fields: [
          {
            name: "progress",
            description: "Work completed in session",
            required: true,
            format: "Progress: ${progress}"
          },
          {
            name: "blockers",
            description: "Issues blocking progress",
            required: false,
            format: "Blockers: ${blockers}"
          },
          {
            name: "decisions",
            description: "Key decisions made",
            required: false,
            format: "Decisions: ${decisions}"
          }
        ]
      },
      handoff: {
        type: "handoff",
        description: "Session completion and handoff details",
        fields: [
          {
            name: "completed_work",
            description: "Summary of completed work",
            required: true,
            format: "Completed: ${completed}"
          },
          {
            name: "code_state",
            description: "Current state of codebase",
            required: true,
            format: "Code State: ${state}"
          },
          {
            name: "environment",
            description: "Development environment state",
            required: true,
            format: "Environment: ${env}"
          },
          {
            name: "unresolved",
            description: "Unresolved issues",
            required: false,
            format: "Unresolved: ${issues}"
          }
        ]
      }
    };
  • TypeScript interfaces defining the structure of templates and fields used in HANDOFF_TEMPLATES.
    export interface TemplateField {
      name: string;
      description: string;
      required: boolean;
      format?: string;
    }
    
    export interface EntityTemplate {
      type: string;
      description: string;
      fields: TemplateField[];
    }
Behavior2/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 states the tool lists templates but doesn't describe any behavioral traits like whether it's read-only, requires authentication, has rate limits, or what the output format might be. This leaves significant gaps for a tool with potential operational implications.

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?

The description is a single, efficient sentence that front-loads the core action and resource without any wasted words. It's appropriately sized for a simple list tool with no parameters.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the lack of annotations and output schema, the description is incomplete. It doesn't address behavioral aspects like safety, output format, or error handling, which are crucial for an AI agent to use this tool effectively in a broader context with sibling tools.

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 no parameter documentation is needed. The description appropriately doesn't discuss parameters, focusing instead on the tool's purpose, which aligns well with the schema's simplicity.

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?

The description clearly states the action ('List') and resource ('available templates'), specifying the template types ('for next steps, working sessions, and handoffs'). However, it doesn't explicitly differentiate from sibling tools like 'get_latest_next_steps' or 'get_next_step_history', which might also involve templates or next steps.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites, timing, or how it relates to sibling tools such as 'create_handoff' or 'start_working_session', leaving the agent to infer usage context independently.

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

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/davidorex/project-handoffs'

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