Skip to main content
Glama

eng-leadership-toolkit

by coach.marian

Developer value & salary calculator

calculate_developer_value
Read-onlyIdempotent

Assess a software developer's market value: score 15 skills across 5 pillars (core craft, systems & judgment, impact & ownership, collaboration & influence, AI leverage), get a weighted total score, seniority level, and a 2026 Western-Europe gross salary estimate. Same logic as the live calculator at marian.coach. Unscored skills default to the level's baseline.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
levelYesThe developer's current (or claimed) level — sets pillar weights and baseline
scoresNoOptional 0-10 score per skill. Valid keys: discipline-mastery, code-quality, debugging, system-design, tech-decisions, data-performance, shipping-outcomes, production-ownership, domain-expertise, communication, mentoring, cross-functional, ai-output, ai-quality, ai-workflows. Omitted skills use the level baseline (junior 3, mid 5, senior 6, staff 7).
contextYesExplain 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."

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
mathNoNapkin math behind the case.
emailNoForwardable email to the manager.
levelNoSeniority level the score maps to, when the tool computes one.
reportYesThe full human-readable report.
sourceYesCanonical marian.coach page this answer is derived from.
verdictNoHeadline verdict, when the tool returns one.
evidenceNoSources the case may cite.
onePagerNoManager-facing one-pager, forwardable to finance.
salaryEurNoEstimated 2026 Western-Europe gross annual salary in EUR.
objectionsNoThe usual objections, answered.
slackShortNoSlack/Teams-length version of the ask.
totalScoreNoWeighted 0-10 score, when the tool computes one.
valueFormulaNoThe four value lines to add up (money saved, cost of delay, missed opportunity, roadmap slippage) plus the count-then-halve CFO rule.
talkingPointsNoFive talking points for the conversation.
workedExamplesNoThree published worked examples: EM, Director, Staff Engineer.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed2 schema fields changed
    • 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: -[
-  "level"
-]New value: +[
+  "level",
+  "context"
+]
  2. Changed9 schema fields changed
    • 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"
+}
  3. Changed1 schema field changed
    • 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"
+}
  4. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already establish that this is a safe, read-only, idempotent operation. The description adds meaningful behavioral context beyond those annotations: the 15 scores are grouped into 5 pillars, there is a weighted total, results include a 2026 regional salary estimate, and unscored skills fall back to the level baseline. It also notes parity with the live marian.coach calculator.

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?

Three sentences carry the purpose, key behavioral rules, and provenance with no redundancy or filler. The most actionable information—what the tool computes and returns—is front-loaded, and the default-behavior note earns its place.

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?

The description covers the scoring model, defaults, output types, and regional/timeframe specificity, while an output schema handles return structure details. It is complete enough for an agent to invoke the tool correctly, though explicit sibling differentiation would make it slightly stronger.

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 schema already documents all three parameters well. The description adds modest value by grouping the 15 skill keys into 5 pillars and restating the baseline default, but it does not substantially explain parameter semantics beyond what the schema provides.

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 opens with a specific verb ('Assess') and resource ('a software developer's market value'), then lists concrete outputs: weighted total score, seniority level, and a 2026 Western-Europe gross salary estimate. This clearly distinguishes it from sibling tools like calculate_engineering_manager_value, which target managers rather than developers.

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 intended use is implied by the first sentence: use this when the goal is to assess a developer's market value, seniority, or salary. However, the description gives no explicit guidance on when to choose this tool over siblings such as assess_team_lead_readiness or calculate_engineering_manager_value, and it names no alternatives.

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 toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.2/5.0
Disambiguation3/5

Most tools have clearly distinct purposes, but get_started and get_more_tools are nearly identical—both handle greetings, liveness tests, and return the full tool menu. This redundancy creates ambiguity about which to call, especially for general queries.

Naming Consistency5/5

All tool names follow a consistent verb_noun snake_case pattern (assess_team_lead_readiness, calculate_developer_value, get_one_on_one_playbook). The verbs are descriptive and consistent, and there is no mixing of conventions.

Tool Count5/5

11 tools is well within the ideal range for a focused domain. Each tool addresses a distinct aspect of engineering leadership mentoring and coaching, from readiness assessment to cost estimation, without feeling bloated or sparse.

Completeness5/5

The toolkit covers the full lifecycle of leadership development: assessment (readiness, value), guidance (first-time manager, 1:1 playbook), decision-making (mentor vs coach), cost estimation, business case building, and benchmarking. The only redundancy (get_started/get_more_tools) is not a gap but a duplication, so no missing capabilities are evident.

Resources