Skip to main content
Glama
davidorex

Project Handoffs MCP Server

by davidorex

get_next_step_history

Retrieve complete history of a project's next step, including session details and handoff information, to track workflow progression and maintain context during transitions.

Instructions

Get complete history of a next step including session and handoff

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
projectIdYesProject identifier
stepIdYesNext step ID

Implementation Reference

  • Core handler function in ProjectManager that loads project data, finds the specified next step, its associated working session, and handoff, then returns them.
    async getNextStepHistory(projectId: string, stepId: string): Promise<{
      step: NextStep;
      session?: WorkingSession;
      handoff?: Handoff;
    }> {
      const data = await this.loadProjectData(projectId);
      
      const step = data.nextSteps.find(s => s.id === stepId);
      if (!step) {
        throw new ProjectError(`Next step not found: ${stepId}`, projectId);
      }
    
      const session = data.workingSessions.find(s => s.nextStepId === stepId);
      const handoff = session ? data.handoffs.find(h => h.sessionId === session.id) : undefined;
    
      return { step, session, handoff };
    }
  • src/index.ts:394-405 (registration)
    Tool registration in the listTools response, defining name, description, and input schema.
    {
      name: "get_next_step_history",
      description: "Get complete history of a next step including session and handoff",
      inputSchema: {
        type: "object",
        properties: {
          projectId: { type: "string", description: "Project identifier" },
          stepId: { type: "string", description: "Next step ID" }
        },
        required: ["projectId", "stepId"]
      }
    }
  • Input schema definition for the get_next_step_history tool, specifying required projectId and stepId parameters.
    inputSchema: {
      type: "object",
      properties: {
        projectId: { type: "string", description: "Project identifier" },
        stepId: { type: "string", description: "Next step ID" }
      },
      required: ["projectId", "stepId"]
    }
  • Dispatcher in CallToolRequestSchema handler that invokes the ProjectManager method and formats the response.
    case "get_next_step_history":
      const history = await projectManager.getNextStepHistory(
        args.projectId as string,
        args.stepId as string
      );
      return {
        content: [{
          type: "text",
          text: JSON.stringify(history, null, 2)
        }]
      };
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states the tool retrieves history data, implying it's a read operation, but doesn't clarify permissions needed, rate limits, pagination, or what 'complete history' entails (e.g., timestamps, changes). This leaves significant gaps for a tool with no annotation coverage.

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 with zero waste. It's front-loaded with the core purpose and includes relevant details (session and handoff) without unnecessary elaboration.

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?

For a tool with no annotations and no output schema, the description is incomplete. It doesn't explain what 'complete history' returns (e.g., structured data, timestamps), behavioral traits like error handling, or how it differs from siblings. This leaves the agent with insufficient context for reliable use.

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 description coverage is 100%, so the schema already documents both parameters (projectId and stepId). The description adds no additional meaning about these parameters beyond what's in the schema, such as format examples or relationships between them. Baseline 3 is appropriate when schema does the heavy lifting.

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 ('Get complete history') and resource ('of a next step'), specifying it includes session and handoff information. However, it doesn't differentiate from sibling tools like 'get_latest_next_steps' or 'start_working_session' that might also retrieve step-related data.

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 like 'get_latest_next_steps' or 'create_handoff'. It mentions what data is included but doesn't specify use cases, prerequisites, or exclusions.

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