Skip to main content
Glama

ELC membership business-case builder

build_partnership_business_case
Read-onlyIdempotent

Builds the internal business case for partnering with Engineering Leaders Community: real reach numbers (3,700+ members, 120+ per meetup, 500+ at the annual conference, newsletter open rate), the deliverables that actually serve the stated goal, where a proposed budget lands on the published ladder, and a forwardable approval email. States the published price RANGE (free layer to EUR 20,000/year, EUR 32,000 with category exclusivity); for composing and pricing an exact package item by item, use the dedicated Membership Builder MCP server at https://www.engineeringleaders.io/mcp/partnership.

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

Input Schema

NameRequiredDescriptionDefault
goalNoRequired. The primary reason to partner with ELC. people_development means developing your own engineering leaders through mentoring and the Academy One of: hiring, brand_awareness, product_feedback, thought_leadership, people_development.
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.
buying_forNoWho is buying. 'company' (default) builds the annual membership case. 'individual' means a person spending their own money — returns the free-membership route, not an approval email. 'one_off' means one thing once rather than a year, and routes to the one-off menu. One of: company, individual, one_off.
sender_nameNoOptional: who the approval email is signed by
company_nameNoOptional: the company considering the membership
approver_nameNoOptional: who the approval email is addressed to. Supplied, it is used in the greeting; omitted, the draft opens with a plain 'Hi,' rather than a placeholder
proposed_budget_eurNoOptional: a proposed budget figure, if one exists yet. 0 is a valid answer and routes to the free membership layer

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. Changed2 schema fields changed
    • addedInput schema / properties / proposed_budget_eur / anyOf
      Added value: +[
      +  {
      +    "type": "number"
      +  },
      +  {
      +    "type": "string"
      +  }
      +]
    • removedInput schema / properties / proposed_budget_eur / type
      Removed value: -"number"
  3. Changed6 schema fields changed
    • changedInput schema / properties / buying_for / description
      Previous value: -"Who is buying. 'company' (default) builds the annual membership case. 'individual' means a person spending their own money — returns the free-membership route, not an approval email. 'one_off' means one thing once rather than a year, and routes to the one-off menu."New value: +"Who is buying. 'company' (default) builds the annual membership case. 'individual' means a person spending their own money — returns the free-membership route, not an approval email. 'one_off' means one thing once rather than a year, and routes to the one-off menu. One of: company, individual, one_off."
    • removedInput schema / properties / buying_for / enum
      Removed value: -[
      -  "company",
      -  "individual",
      -  "one_off"
      -]
    • 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 / goal / description
      Previous value: -"The primary reason to partner with ELC. One of: hiring, brand_awareness, product_feedback, thought_leadership, people_development (developing your own engineering leaders through mentoring and the Academy)"New value: +"Required. The primary reason to partner with ELC. people_development means developing your own engineering leaders through mentoring and the Academy One of: hiring, brand_awareness, product_feedback, thought_leadership, people_development."
    • removedInput schema / properties / goal / enum
      Removed value: -[
      -  "hiring",
      -  "brand_awareness",
      -  "product_feedback",
      -  "thought_leadership",
      -  "people_development"
      -]
    • removedInput schema / required
      Removed value: -[
      -  "goal",
      -  "context"
      -]
  4. Changed1 schema field changed
    • addedInput schema / properties / buying_for
      Added value: +{
      +  "description": "Who is buying. 'company' (default) builds the annual membership case. 'individual' means a person spending their own money — returns the free-membership route, not an approval email. 'one_off' means one thing once rather than a year, and routes to the one-off menu.",
      +  "enum": [
      +    "company",
      +    "individual",
      +    "one_off"
      +  ],
      +  "type": "string"
      +}
  5. Changed5 schema fields changed
    • addedInput schema / properties / approver_name
      Added value: +{
      +  "description": "Optional: who the approval email is addressed to. Supplied, it is used in the greeting; omitted, the draft opens with a plain 'Hi,' rather than a placeholder",
      +  "type": "string"
      +}
    • changedInput schema / properties / goal / description
      Previous value: -"The primary reason to partner with ELC"New value: +"The primary reason to partner with ELC. One of: hiring, brand_awareness, product_feedback, thought_leadership, people_development (developing your own engineering leaders through mentoring and the Academy)"
    • changedInput schema / properties / goal / enum
      Previous value: -[
      -  "hiring",
      -  "brand_awareness",
      -  "product_feedback",
      -  "thought_leadership"
      -]New value: +[
      +  "hiring",
      +  "brand_awareness",
      +  "product_feedback",
      +  "thought_leadership",
      +  "people_development"
      +]
    • changedInput schema / properties / proposed_budget_eur / description
      Previous value: -"Optional: a proposed budget figure, if one exists yet, to frame the per-outcome bar against"New value: +"Optional: a proposed budget figure, if one exists yet. 0 is a valid answer and routes to the free membership layer"
    • addedInput schema / properties / sender_name
      Added value: +{
      +  "description": "Optional: who the approval email is signed by",
      +  "type": "string"
      +}
  6. 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: -[
      -  "goal"
      -]New value: +[
      +  "goal",
      +  "context"
      +]
  7. Changed1 schema field changed
    • changedInput schema / properties / company_name / description
      Previous value: -"Optional: the company considering the partnership"New value: +"Optional: the company considering the membership"
  8. First observed

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true and openWorldHint=false, so the safety profile is fully carried by structured data and the description correctly adds nothing contradictory. It does add useful behavioral context, namely that it returns a draft approval email and states a price RANGE rather than quoting an exact package. With annotations doing the heavy lifting on mutation and side effects, this is solid but not exceptional.

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 output inventory is front-loaded in the first sentence and the alternative route is placed last, which is good ordering. The parenthetical reach statistics ('3,700+ members, 120+ per meetup, 500+ at the annual conference') are the weakest element, since they preview return values rather than helping the agent decide or call, but they are compact and arguably useful.

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?

For a read-only, non-open-world builder with no output schema, the description covers what the agent needs: the four artifacts produced, the fact that prices are stated as a range bounded by free and EUR 32,000 with exclusivity, and where to go for exact itemized pricing. It is not fully complete because it never says what happens when goal is omitted (required parameters are listed as zero) or how the return is structured for downstream consumption.

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%, so the schema already explains goal, buying_for routes, budget of 0, and the placeholder behavior when approver_name is omitted; the baseline of 3 applies. The description adds only indirect meaning here: the price range implies that proposed_budget_eur is compared against a published ladder rather than used to generate a quote. It never mentions any parameter by name or clarifies the individual/one_off routing beyond what the schema states.

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 and resource ('Builds the internal business case for partnering with Engineering Leaders Community') and then enumerates the concrete outputs: reach numbers, deliverables matched to the goal, budget placement on the published ladder, and a forwardable approval email. That is far more specific than the title alone and lets an agent tell this apart from the sibling tools, which cover unrelated topics (launch readiness, leadership ratio, career path).

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?

It gives an explicit alternative and the condition that selects it: for 'composing and pricing an exact package item by item, use the dedicated Membership Builder MCP server' at a named URL. What it does not do is state an exclusion condition in terms of the sibling tools in this server (e.g., when to prefer plan_leadership_career_path over a membership case) or say when this tool is not appropriate at all, so it falls short of a full when/when-not pair.

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.