Skip to main content
Glama

elc-toolkit

by io.engineeringleaders
OverviewDiscussionsAdmin

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,300+ 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 — inquiries sent through it carry a 16% AI-channel discount.

Input Schema

TableJSON 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

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
reportYesThe full human-readable report.
sourceYesCanonical engineeringleaders.io page this answer is derived from.
verdictNoHeadline verdict, when the tool returns one.

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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"
  2. 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"
-]
  3. 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"
+}
  4. 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"
+}
  5. 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"
+]
  6. 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"
  7. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the safety profile is covered. The description adds value beyond them: the published price RANGE (free layer to EUR 20,000/year, EUR 32,000 with exclusivity) and the 16% AI-channel discount, which an agent could not infer from structured fields. It stops short of describing rate limits or output format, hence not a 5.

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?

Front-loads what the tool produces before the scope/pricing details and the alternative route. It is dense but each clause carries information; the reach-number enumeration is slightly padded but still substantive.

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 an output schema present, return values need no explanation, and the description covers scope, pricing range, routing to the alternative server, and output nature (a forwardable draft email). Nothing an agent needs to invoke it correctly is missing, though it does not address turnaround or failure modes.

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 7 parameters are self-documenting (goal enums, buying_for routing, budget '0 is a valid answer'). The description reinforces the budget-ladder behavior but adds no new syntax or per-parameter meaning beyond what the schema already supplies, so the baseline 3 applies.

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 ('Builds the internal business case for partnering with Engineering Leaders Community') and enumerates the concrete outputs: reach numbers, goal-aligned deliverables, budget-ladder placement, and a forwardable approval email. It also distinguishes itself from the sibling Membership Builder MCP server for exact item-by-item pricing, so an agent can tell the two apart without opening a 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 names the alternative explicitly ('for composing and pricing an exact package item by item, use the dedicated Membership Builder MCP server at ...') with the condition that selects it, and notes the AI-channel discount tied to that route. Combined with the buying_for routing documented in the schema, the when-to-use picture is unambiguous.

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

All elc-toolkit toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources