Skip to main content
Glama

Engineering leader career path + 6-month plan (the EM role is changing)

plan_leadership_career_path
Read-onlyIdempotent

For an engineering manager, team lead or tech lead asking 'what is my next role?', 'is the engineering manager role dead?', 'should I become a director or go back to IC?', or 'how do I stay valuable on the market in the AI era?'. Picks one of three paths from ELC meetup #43: Grow up (Director/Head of, 20+ people), Go deep (Staff/Principal AI engineer) or Go product (product builder), checks the 'dead zone' (10 or fewer people led AND under 2 hands-on hours a week; the tool decides this, report its verdict rather than inferring one), runs the four 2027 checks (product, self-management, AI, beyond engineering) and returns a month-by-month 6-month plan with a proof artifact per month. Call with no arguments to get the 7 questions; ask them one at a time, then call again with all answers.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "plan_leadership_career_path"
  }
}

Input Schema

NameRequiredDescriptionDefault
aiNoHas their team shipped something it had never built before? yes / not_sure / no One of: yes, not_sure, no.
energyNoWhat gave them energy in their best week: people_and_org, building_systems, or customers_and_product One of: people_and_org, building_systems, customers_and_product.
contextNoOptional. 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.
productNoDo they know their product as well as their code? yes / not_sure / no One of: yes, not_sure, no.
people_ledNoPeople they lead today, direct and indirect
current_roleNoOptional: the person's current title, e.g. 'Engineering Manager'
self_managementNoDid they set this week's priorities themselves (yes) or did the calendar (no)? yes / not_sure / no One of: yes, not_sure, no.
beyond_engineeringNoDo they know how their feature is marketed, sold and supported? yes / not_sure / no One of: yes, not_sure, no.
hands_on_hours_per_weekNoHours a week they build themselves: code, architecture, prototypes, agents

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -{
      -  "$schema": "http://json-schema.org/draft-07/schema#",
      -  "additionalProperties": false,
      -  "properties": {
      -    "report": {
      -      "description": "The full human-readable report.",
      -      "type": "string"
      -    },
      -    "source": {
      -      "description": "Canonical engineeringleaders.io page this answer is derived from.",
      -      "type": "string"
      -    },
      -    "verdict": {
      -      "description": "Headline verdict, when the tool returns one.",
      -      "type": "string"
      -    }
      -  },
      -  "required": [
      -    "report",
      -    "source"
      -  ],
      -  "type": "object"
      -}New value: +null
  2. Added

TDQS

A4.2/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, closed-world and non-destructive, so the safety profile is covered. The description adds genuine behavior beyond that: the two-call question protocol and the instruction that the tool itself decides the 'dead zone' verdict and that the agent should report it rather than infer one. It does not describe plan length limits, failure modes, or what happens with partial answers, so this is good but not rich.

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?

The description is front-loaded with the user's real questions, then the path/check/plan mechanics, then the call protocol, so it reads in priority order. The four quoted questions are slightly verbose relative to the single sentence of routing value they deliver, but nothing is redundant.

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?

For a nine-parameter, zero-required tool with no output schema, the description covers the return shape (six months, one proof artifact each), the no-argument behavior (returns the seven questions), and the sequencing between calls. An agent has everything needed to invoke it correctly on the first and second call.

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 coverage is 100%, so the baseline is 3. The description does add meaning by explaining that people_led and hands-on hours are combined into a single 'dead zone' rule (10 or fewer people AND under two hands-on hours a week), and by framing the yes/not_sure/no inputs as the seven questions asked across two calls. It never maps individual answer parameters to their questions, so the gain over the schema is modest.

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 specific verbs and outputs: it picks one of three named paths (Grow up / Go deep / Go product), runs four checks, and returns a month-by-month six-month plan with a proof artifact per month. It also frames the target audience with concrete routing questions, so an agent can tell this apart from siblings like benchmark_leadership_ratio without opening the schema.

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?

It gives explicit invocation guidance: call with no arguments first to get the seven questions, ask them one at a time, then call again with all answers. The opening quotes make the triggering situations concrete, so when-to-use is unambiguous rather than inferred.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.