agentic-sdlc-mcp

Agent Handoff Packet

agent_handoff_packet

Read-onlyIdempotent

Wrap up a session by generating a compact handoff packet with goals, decisions, completed actions, and next steps so another AI agent can continue SDLC work with full context.

Instructions

Generate a compact handoff packet so another AI agent can continue SDLC work.

Use when wrapping up a session, before handing off to a specialised agent, or when context is nearing its limit.

Args:

owner, repo: Repository coordinates.
issueNumber (number?): Issue being worked on.
pullNumber (number?): PR being worked on.
releaseRef (string?): Release ref being worked on.
currentStatus (string?): Optional caller-authored status; system evidence is used when omitted.
goal / nonGoals / completedActions / decisions: Optional caller-authored handoff context.
nextSteps (string[]?): Ordered tasks for the next agent.

Returns: Compact handoff prompt, repo context snapshot, and remaining tasks.

Input Schema

TableJSON Schema

Name	Required	Description
`goal`	No	Optional caller-authored goal. Kept unverified.
`repo`	No	GitHub repo. Falls back to GITHUB_REPO.
`owner`	No	GitHub owner. Falls back to GITHUB_OWNER.
`nonGoals`	No	Optional caller-authored non-goals. Kept unverified.
`decisions`	No	Optional caller-authored decisions. Kept unverified.
`nextSteps`	No	Ordered list of next steps for the incoming agent.
`pullNumber`	No	PR being worked on (if applicable).
`releaseRef`	No	Release ref being worked on (if applicable).
`issueNumber`	No	Issue being worked on (if applicable).
`currentStatus`	No	Optional caller-authored work status. Kept unverified.
`completedActions`	No	Optional caller-authored completed actions. Kept unverified.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`goal`	Yes
`repo`	Yes
`prRef`	Yes
`issueRef`	Yes
`nonGoals`	Yes
`decisions`	Yes
`nextSteps`	Yes
`releaseRef`	Yes
`policyDigest`	No
`currentStatus`	Yes
`defaultBranch`	Yes
`handoffPrompt`	Yes
`policySources`	No
`policySummary`	No
`trustBoundary`	No
`evidencePacket`	Yes
`policyDegraded`	No
`completedActions`	Yes
`evidenceWarnings`	Yes
`appliedPolicyRules`	No
`promptInjectionWarnings`	Yes

Tool Definition Quality

A4.7/5.0

Behavior5/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and non-destructive. The description adds beyond: explains that missing 'currentStatus' uses system evidence, and caller-authored fields are 'kept unverified'. No contradictions.

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 brief (intro, usage, param list) with no wasted sentences. Every part contributes to understanding the tool's use and parameters.

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 11 optional parameters, high schema coverage, annotations, and mention of output, the description is complete. It states what returns (handoff prompt, repo context, remaining tasks) which suffices.

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?

Schema description coverage is 100%, so the schema itself documents all parameters. However, the description adds value by explaining fallback behavior for 'currentStatus' and that optional fields are unverified, which goes beyond schema descriptions.

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 states the specific verb 'Generate' and resource 'handoff packet' with clear purpose for another AI agent to continue SDLC work. It distinguishes itself from siblings like 'sdlc_evidence_packet' by focusing on handoff context.

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?

The description explicitly states when to use: wrapping up a session, before handoff to a specialised agent, or when context is near limit. It does not mention alternative tools or when not to use, but the context is clear enough for correct selection.

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

Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)
By Om-Shree-0709 on July 25, 2026.
mcp
Agent Identity
OAuth 2.1
Your AI Chatbot Just Exposed Your CEO's Salary to an Intern
By Om-Shree-0709 on July 2, 2026.
Agent Identity
MCP Security
OAuth Delegation
Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)
By Om-Shree-0709 on June 30, 2026.
Agentic Ai
Prompt Injection
WebAssembly

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/SakuraCianna/agentic-sdlc-mcp'

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