Skip to main content
Glama

Engineering org leadership-ratio benchmark

benchmark_leadership_ratio
Read-onlyIdempotent

Describes a company's manager-vs-senior-IC split — each side's percentage, the resulting span (1 manager per N senior ICs), and the question that shape usually raises. Alongside it, for context rather than as a target, ELC's own community composition (69% Manager+/Leadership, 21% Senior/Staff IC across 3,700+ CEE engineering leaders — that is who joins a leadership community, not a survey of org structures, so there is deliberately no score against it). Count the SAME population on both sides: senior people who could plausibly hold a management role (managers, tech leads, senior/staff ICs), leaving out junior/mid ICs.

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": "benchmark_leadership_ratio"
  }
}

Input Schema

NameRequiredDescriptionDefault
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.
managersNoRequired. Count of people in Manager+/Leadership roles
senior_icsNoRequired. Count of Senior/Staff-level individual contributors (not junior/mid)

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. Changed6 schema fields changed
    • addedInput schema / properties / managers / anyOf
      Added value: +[
      +  {
      +    "type": "number"
      +  },
      +  {
      +    "type": "string"
      +  }
      +]
    • removedInput schema / properties / managers / minimum
      Removed value: -0
    • removedInput schema / properties / managers / type
      Removed value: -"number"
    • addedInput schema / properties / senior_ics / anyOf
      Added value: +[
      +  {
      +    "type": "number"
      +  },
      +  {
      +    "type": "string"
      +  }
      +]
    • removedInput schema / properties / senior_ics / minimum
      Removed value: -0
    • removedInput schema / properties / senior_ics / type
      Removed value: -"number"
  3. Changed4 schema fields changed
    • 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 / managers / description
      Previous value: -"Count of people in Manager+/Leadership roles"New value: +"Required. Count of people in Manager+/Leadership roles"
    • changedInput schema / properties / senior_ics / description
      Previous value: -"Count of Senior/Staff-level individual contributors (not junior/mid)"New value: +"Required. Count of Senior/Staff-level individual contributors (not junior/mid)"
    • removedInput schema / required
      Removed value: -[
      -  "managers",
      -  "senior_ics",
      -  "context"
      -]
  4. 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: -[
      -  "managers",
      -  "senior_ics"
      -]New value: +[
      +  "managers",
      +  "senior_ics",
      +  "context"
      +]
  5. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover the safety profile (read-only, idempotent, closed-world), so the description's job is to add context — and it does: it discloses that the output includes the ratio, the span, and the question that shape raises, and it explicitly says ELC's 69/21 composition is context, not a target, with no score computed against it. That last point prevents a real misinterpretation an agent could otherwise make. It is only slightly short of a 5 because the 'question that shape usually raises' is mentioned but never characterized.

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

Conciseness3/5

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

It is front-loaded with the core behavior, but the second half is a long parenthetical digression about ELC's community makeup and its 3,700+ members that costs the reader more than it returns. The counting instruction, arguably the most actionable sentence, is buried at the end instead of being placed next to the parameters it governs.

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?

With no output schema, the description carries the burden of explaining what comes back, and it does name the percentage split, the span ratio, and the interpretive question. The counting rule closes the main correctness risk for a two-number input. What remains thin is the exact shape of the returned interpretation, but for a small read-only calculator this is close to sufficient.

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 coverage is 100%, so the baseline is 3, but the description genuinely adds meaning beyond the schema: it defines who belongs in each bucket (managers, tech leads, senior/staff ICs) and insists both sides be counted over the same population. The schema's own note that senior_ics excludes junior/mid is reinforced and expanded rather than repeated. The optional context parameter is not discussed, which keeps it out of 5 territory.

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?

States a specific verb and resource: it describes a company's manager-vs-senior-IC split, including percentages and resulting span ratio. That is concrete enough for an agent to distinguish it from the career-path and community-readiness siblings. The leading verb 'Describes' is a little soft, but the resource is unambiguous.

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 description gives a real usage rule — count the same population on both sides, including managers, tech leads, and senior/staff ICs while excluding junior/mid ICs. It never says when to reach for this tool instead of a sibling, nor what conditions make a benchmark call appropriate. Usage is implied rather than routed.

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.