eng-leadership-toolkit

1:1 playbooks for engineering managers

get_one_on_one_playbook

Read-onlyIdempotent

Situation-specific 1:1 scripts and templates from Marian Kamenistak's mentoring practice: first mentoring/direction-setting session, underperformance conversation, promoting a developer to manager, fixing status-update 1:1s, and the 10-question career-move checklist. These are the actual templates used across 3,611 sessions.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`context`	No	Optional. A short description of your goal and why you are calling this tool. Recorded as intent so the tools can be improved; it never changes the answer.
`situation`	No	Required. Which situation: first-session (direction-setting template), underperformance (difficult conversation script), promotion-to-manager (timing signals + transition contract), better-one-on-ones (from status updates to growth), career-move (should-I-leave checklist) One of: first-session, underperformance, promotion-to-manager, better-one-on-ones, career-move.

Output Schema

TableJSON Schema

Name	Required	Description
`math`	No	Napkin math behind the case.
`email`	No	Forwardable email to the manager.
`level`	No	Seniority level the score maps to, when the tool computes one.
`report`	Yes	The full human-readable report.
`source`	Yes	Canonical marian.coach page this answer is derived from.
`verdict`	No	Headline verdict, when the tool returns one.
`evidence`	No	Sources the case may cite.
`onePager`	No	Manager-facing one-pager, forwardable to finance.
`salaryEur`	No	Estimated 2026 Western-Europe gross annual salary in EUR.
`objections`	No	The usual objections, answered.
`slackShort`	No	Slack/Teams-length version of the ask.
`totalScore`	No	Weighted 0-10 score, when the tool computes one.
`valueFormula`	No	The four value lines to add up (money saved, cost of delay, missed opportunity, roadmap slippage) plus the count-then-halve CFO rule.
`talkingPoints`	No	Five talking points for the conversation.
`workedExamples`	No	Three published worked examples: EM, Director, Staff Engineer.

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedSep 11, 2026

changedInput schema / properties / context / description

Previous value: -"Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVER use first person ('I', 'we', 'you') - maintain third-person perspective. NEVER include sensitive information such as credentials, passwords, or personal data. Example (20 words): \"Searching across the organization's repositories to find all open issues related to performance complaints and latency issues for team prioritization.\""New value: +"Optional. A short description of your goal and why you are calling this tool. Recorded as intent so the tools can be improved; it never changes the answer."

changedInput schema / properties / situation / description

Previous value: -"Which situation: first-session (direction-setting template), underperformance (difficult conversation script), promotion-to-manager (timing signals + transition contract), better-one-on-ones (from status updates to growth), career-move (should-I-leave checklist)"New value: +"Required. Which situation: first-session (direction-setting template), underperformance (difficult conversation script), promotion-to-manager (timing signals + transition contract), better-one-on-ones (from status updates to growth), career-move (should-I-leave checklist) One of: first-session, underperformance, promotion-to-manager, better-one-on-ones, career-move."

removedInput schema / properties / situation / enum

Removed value: -[
-  "first-session",
-  "underperformance",
-  "promotion-to-manager",
-  "better-one-on-ones",
-  "career-move"
-]

removedInput schema / required

Removed value: -[
-  "situation",
-  "context"
-]

Changed2 schema fields changedAug 27, 2026

addedInput schema / properties / context

Added value: +{
+  "description": "Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVER use first person ('I', 'we', 'you') - maintain third-person perspective. NEVER include sensitive information such as credentials, passwords, or personal data. Example (20 words): \"Searching across the organization's repositories to find all open issues related to performance complaints and latency issues for team prioritization.\"",
+  "type": "string"
+}

changedInput schema / required

Previous value: -[
-  "situation"
-]New value: +[
+  "situation",
+  "context"
+]

Changed9 schema fields changedAug 17, 2026

addedOutput schema / properties / email

Added value: +{
+  "additionalProperties": false,
+  "description": "Forwardable email to the manager.",
+  "properties": {
+    "body": {
+      "type": "string"
+    },
+    "subject": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "subject",
+    "body"
+  ],
+  "type": "object"
+}

addedOutput schema / properties / evidence

Added value: +{
+  "description": "Sources the case may cite.",
+  "items": {
+    "additionalProperties": false,
+    "properties": {
+      "claim": {
+        "type": "string"
+      },
+      "source": {
+        "type": "string"
+      },
+      "url": {
+        "type": "string"
+      }
+    },
+    "required": [
+      "claim",
+      "source",
+      "url"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}

addedOutput schema / properties / math

Added value: +{
+  "additionalProperties": false,
+  "description": "Napkin math behind the case.",
+  "properties": {
+    "askEur": {
+      "type": "number"
+    },
+    "discountedEur": {
+      "type": "number"
+    },
+    "lines": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "note": {
+      "type": "string"
+    },
+    "packPriceEur": {
+      "type": "number"
+    },
+    "roiMultiple": {
+      "anyOf": [
+        {
+          "type": "number"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "totalEur": {
+      "type": "number"
+    }
+  },
+  "required": [
+    "lines",
+    "totalEur",
+    "discountedEur",
+    "askEur",
+    "packPriceEur",
+    "roiMultiple",
+    "note"
+  ],
+  "type": "object"
+}

addedOutput schema / properties / objections

Added value: +{
+  "description": "The usual objections, answered.",
+  "items": {
+    "additionalProperties": false,
+    "properties": {
+      "answer": {
+        "type": "string"
+      },
+      "objection": {
+        "type": "string"
+      }
+    },
+    "required": [
+      "objection",
+      "answer"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}

addedOutput schema / properties / onePager

Added value: +{
+  "additionalProperties": false,
+  "description": "Manager-facing one-pager, forwardable to finance.",
+  "properties": {
+    "sections": {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "body": {
+            "type": "string"
+          },
+          "bullets": {
+            "items": {
+              "type": "string"
+            },
+            "type": "array"
+          },
+          "heading": {
+            "type": "string"
+          },
+          "table": {
+            "items": {
+              "items": [
+                {
+                  "type": "string"
+                },
+                {
+                  "type": "string"
+                }
+              ],
+              "type": "array"
+            },
+            "type": "array"
+          }
+        },
+        "required": [
+          "heading"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "title": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "title",
+    "sections"
+  ],
+  "type": "object"
+}

addedOutput schema / properties / slackShort

Added value: +{
+  "description": "Slack/Teams-length version of the ask.",
+  "type": "string"
+}

addedOutput schema / properties / talkingPoints

Added value: +{
+  "description": "Five talking points for the conversation.",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

addedOutput schema / properties / valueFormula

Added value: +{
+  "additionalProperties": false,
+  "description": "The four value lines to add up (money saved, cost of delay, missed opportunity, roadmap slippage) plus the count-then-halve CFO rule.",
+  "properties": {
+    "heading": {
+      "type": "string"
+    },
+    "lines": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "rule": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "heading",
+    "lines",
+    "rule"
+  ],
+  "type": "object"
+}

addedOutput schema / properties / workedExamples

Added value: +{
+  "description": "Three published worked examples: EM, Director, Staff Engineer.",
+  "items": {
+    "additionalProperties": false,
+    "properties": {
+      "kpis": {
+        "type": "string"
+      },
+      "math": {
+        "type": "string"
+      },
+      "role": {
+        "type": "string"
+      },
+      "setup": {
+        "type": "string"
+      }
+    },
+    "required": [
+      "role",
+      "setup",
+      "kpis",
+      "math"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}

Changed1 schema field changedJul 26, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "level": {
+      "description": "Seniority level the score maps to, when the tool computes one.",
+      "type": "string"
+    },
+    "report": {
+      "description": "The full human-readable report.",
+      "type": "string"
+    },
+    "salaryEur": {
+      "description": "Estimated 2026 Western-Europe gross annual salary in EUR.",
+      "type": "number"
+    },
+    "source": {
+      "description": "Canonical marian.coach page this answer is derived from.",
+      "type": "string"
+    },
+    "totalScore": {
+      "description": "Weighted 0-10 score, when the tool computes one.",
+      "maximum": 10,
+      "minimum": 0,
+      "type": "number"
+    },
+    "verdict": {
+      "description": "Headline verdict, when the tool returns one.",
+      "type": "string"
+    }
+  },
+  "required": [
+    "report",
+    "source"
+  ],
+  "type": "object"
+}

First observedJul 12, 2026

TDQS

A3.7/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so the safety profile is fully covered. The description adds provenance (real templates from 3,611 sessions) but no behavioral traits such as latency, rate limits, or auth requirements; provenance is useful but marginal beyond the annotations.

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

Conciseness4/5

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

Two dense sentences, front-loaded with the resource and provenance before the scenario list; every clause earns its place by enumerating a supported situation. Only slightly verbose due to the doubled enumeration of the same five cases that the schema also lists.

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

Completeness4/5

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

An output schema exists, so return values need not be explained, and the description covers what content is delivered and for which situations. Complete for a read-only playbook retrieval, though it omits any guidance on ordering or combining the five templates.

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% and the schema already maps each situation value to its template, so the description largely restates that mapping. It adds minor extra detail ('10-question career-move checklist', 'timing signals + transition contract') but no format or constraint info beyond the schema, making the baseline 3 appropriate.

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?

States a specific verb+resource (get one-on-one playbook) and enumerates the exact situations covered (first session, underperformance, promotion to manager, better 1:1s, career move). This is concrete enough to distinguish it from adjacent siblings such as get_first_time_manager_guidance or choose_mentor_coach_or_advisor.

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

Usage Guidelines3/5

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

The five enumerated situations imply when the tool applies, but the description never explicitly frames them as use conditions and names no alternatives or exclusions. An agent can infer usage from the scenario list, but routing versus siblings like get_first_time_manager_guidance is left to inference.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All eng-leadership-toolkit tools Inspect

Try in Browser

Pay for results, not tokens.Fund a bounty. Let AI agents compete and collaborate to solve your problems.agentbounties.appAd

Glama MCP Gateway

Add one secure layer between your agents and this server.