Skip to main content
Glama

elc-partnership-builder

by io.engineeringleaders
OverviewDiscussionsAdmin

Send the composed offer to ELC

request_offer

The ONLY tool that collects contact details. Sends the itemized offer to the visitor's email, notifies Marian (email + Slack), and files the company into ELC's partners queue. Ask for name, work email and company only when the visitor says they want the offer — never earlier. After success: share the confirmation, then make ONE optional ask: would they post publicly (LinkedIn/X) about building their membership with AI? Optional means optional — the discount is already theirs.

Input Schema

NameRequiredDescriptionDefault
kpisNoOptional: what they need to move this year, in their words
nameNoRequired. Visitor's full name
emailNoRequired. Work email the offer goes to
companyNoRequired. Company name
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.
item_idsNoRequired. The final basket: item ids toggled ON
preset_idNoRequired. One of: free, team-seats, starter, pilot-meetup, hiring-meetup, intro-sprint, launch-audit, community-launch, launch-run, hiring, education, vital, visibility, story, product.
visibility_interestNoFrom the discovery question: do they want to invest in their visibility through the cooperation — as a company, through individual leaders, or stay quiet? One of: company, individual, quiet, undecided.
final_price_confirmedNoRequired. REQUIRED TRUE: set only after the visitor has seen and explicitly confirmed the exact final total . Sending without this confirmation is refused.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / preset_id / description
      Previous value: -"Required. One of: free, starter, leadership-pilot, pilot-meetup, hiring-meetup, intro-sprint, launch-audit, community-launch, launch-run, hiring, education, vital, visibility, story, product."New value: +"Required. One of: free, team-seats, starter, pilot-meetup, hiring-meetup, intro-sprint, launch-audit, community-launch, launch-run, hiring, education, vital, visibility, story, product."
  2. Changed1 schema field changed
    • changedInput schema / properties / preset_id / description
      Previous value: -"Required. One of: free, starter, leadership-pilot, pilot-meetup, launch-audit, community-launch, launch-run, hiring, education, vital, visibility, story, product."New value: +"Required. One of: free, starter, leadership-pilot, pilot-meetup, hiring-meetup, intro-sprint, launch-audit, community-launch, launch-run, hiring, education, vital, visibility, story, product."
  3. Changed1 schema field changed
    • changedInput schema / properties / preset_id / description
      Previous value: -"Required. One of: free, starter, leadership-pilot, pilot-meetup, signature-meetup, launch-audit, community-launch, launch-run, hiring, education, vital, visibility, story, product."New value: +"Required. One of: free, starter, leadership-pilot, pilot-meetup, launch-audit, community-launch, launch-run, hiring, education, vital, visibility, story, product."
  4. Changed1 schema field changed
    • changedInput schema / properties / final_price_confirmed / description
      Previous value: -"Required. REQUIRED TRUE: set only after the visitor has seen and explicitly confirmed the exact final total (the discounted figure if the discount applies). Sending without this confirmation is refused."New value: +"Required. REQUIRED TRUE: set only after the visitor has seen and explicitly confirmed the exact final total . Sending without this confirmation is refused."
  5. Changed1 schema field changed
    • changedInput schema / properties / preset_id / description
      Previous value: -"Required. One of: free, starter, leadership-pilot, pilot-meetup, hiring, education, vital, visibility, story, product."New value: +"Required. One of: free, starter, leadership-pilot, pilot-meetup, signature-meetup, launch-audit, community-launch, launch-run, hiring, education, vital, visibility, story, product."
  6. Changed16 schema fields changed
    • changedInput schema / properties / company / description
      Previous value: -"Company name"New value: +"Required. Company name"
    • 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 / email / description
      Previous value: -"Work email the offer goes to"New value: +"Required. Work email the offer goes to"
    • addedInput schema / properties / final_price_confirmed / anyOf
      Added value: +[
+  {
+    "type": "boolean"
+  },
+  {
+    "type": "string"
+  }
+]
    • changedInput schema / properties / final_price_confirmed / description
      Previous value: -"REQUIRED TRUE: set only after the visitor has seen and explicitly confirmed the exact final total (the discounted figure if the discount applies). Sending without this confirmation is refused."New value: +"Required. REQUIRED TRUE: set only after the visitor has seen and explicitly confirmed the exact final total (the discounted figure if the discount applies). Sending without this confirmation is refused."
    • removedInput schema / properties / final_price_confirmed / type
      Removed value: -"boolean"
    • addedInput schema / properties / item_ids / anyOf
      Added value: +[
+  {
+    "items": {
+      "type": "string"
+    },
+    "type": "array"
+  },
+  {
+    "type": "string"
+  }
+]
    • changedInput schema / properties / item_ids / description
      Previous value: -"The final basket: item ids toggled ON"New value: +"Required. The final basket: item ids toggled ON"
    • removedInput schema / properties / item_ids / items
      Removed value: -{
-  "type": "string"
-}
    • removedInput schema / properties / item_ids / type
      Removed value: -"array"
    • changedInput schema / properties / name / description
      Previous value: -"Visitor's full name"New value: +"Required. Visitor's full name"
    • addedInput schema / properties / preset_id / description
      Added value: +"Required. One of: free, starter, leadership-pilot, pilot-meetup, hiring, education, vital, visibility, story, product."
    • removedInput schema / properties / preset_id / enum
      Removed value: -[
-  "free",
-  "starter",
-  "leadership-pilot",
-  "pilot-meetup",
-  "hiring",
-  "education",
-  "vital",
-  "visibility",
-  "story",
-  "product"
-]
    • changedInput schema / properties / visibility_interest / description
      Previous value: -"From the discovery question: do they want to invest in their visibility through the cooperation — as a company, through individual leaders, or stay quiet?"New value: +"From the discovery question: do they want to invest in their visibility through the cooperation — as a company, through individual leaders, or stay quiet? One of: company, individual, quiet, undecided."
    • removedInput schema / properties / visibility_interest / enum
      Removed value: -[
-  "company",
-  "individual",
-  "quiet",
-  "undecided"
-]
    • removedInput schema / required
      Removed value: -[
-  "name",
-  "email",
-  "company",
-  "final_price_confirmed",
-  "preset_id",
-  "item_ids",
-  "context"
-]
  7. 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: -[
-  "name",
-  "email",
-  "company",
-  "final_price_confirmed",
-  "preset_id",
-  "item_ids"
-]New value: +[
+  "name",
+  "email",
+  "company",
+  "final_price_confirmed",
+  "preset_id",
+  "item_ids",
+  "context"
+]
  8. Changed1 schema field changed
    • changedInput schema / properties / preset_id / enum
      Previous value: -[
-  "free",
-  "leadership-pilot",
-  "pilot-meetup",
-  "team",
-  "vital",
-  "hiring",
-  "visibility",
-  "education",
-  "product",
-  "story"
-]New value: +[
+  "free",
+  "starter",
+  "leadership-pilot",
+  "pilot-meetup",
+  "hiring",
+  "education",
+  "vital",
+  "visibility",
+  "story",
+  "product"
+]
  9. Changed1 schema field changed
    • changedInput schema / properties / preset_id / enum
      Previous value: -[
-  "free",
-  "leadership-pilot",
-  "pilot-meetup",
-  "vital",
-  "hiring",
-  "visibility",
-  "education",
-  "product",
-  "story"
-]New value: +[
+  "free",
+  "leadership-pilot",
+  "pilot-meetup",
+  "team",
+  "vital",
+  "hiring",
+  "visibility",
+  "education",
+  "product",
+  "story"
+]
  10. Changed1 schema field changed
    • changedInput schema / properties / preset_id / enum
      Previous value: -[
-  "free",
-  "leadership-pilot",
-  "pilot-meetup",
-  "orbit",
-  "nebula",
-  "supernova",
-  "quasar"
-]New value: +[
+  "free",
+  "leadership-pilot",
+  "pilot-meetup",
+  "vital",
+  "hiring",
+  "visibility",
+  "education",
+  "product",
+  "story"
+]
  11. Changed2 schema fields changed
    • addedInput schema / properties / final_price_confirmed
      Added value: +{
+  "description": "REQUIRED TRUE: set only after the visitor has seen and explicitly confirmed the exact final total (the discounted figure if the discount applies). Sending without this confirmation is refused.",
+  "type": "boolean"
+}
    • changedInput schema / required
      Previous value: -[
-  "name",
-  "email",
-  "company",
-  "preset_id",
-  "item_ids"
-]New value: +[
+  "name",
+  "email",
+  "company",
+  "final_price_confirmed",
+  "preset_id",
+  "item_ids"
+]
  12. Changed1 schema field changed
    • addedInput schema / properties / visibility_interest
      Added value: +{
+  "description": "From the discovery question: do they want to invest in their visibility through the cooperation — as a company, through individual leaders, or stay quiet?",
+  "enum": [
+    "company",
+    "individual",
+    "quiet",
+    "undecided"
+  ],
+  "type": "string"
+}
  13. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations only say non-readonly, non-destructive, non-idempotent, open-world; the description adds real substance beyond that — outbound email, an internal Slack+email notification, and a CRM queue write. It also discloses a hard refusal path ('Sending without this confirmation is refused') tied to final_price_confirmed. Not a 5 only because it never addresses duplicate/idempotency impact or what happens on partial failure.

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-loaded with the identity and side effects, then the collection gate, then the post-call script. Dense but nearly every clause is actionable. The closing social-post script ('would they post publicly... on LinkedIn/X') is slightly more conversational-copy than tool semantics and could be trimmed without loss.

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?

A 9-parameter, non-idempotent, side-effecting commit tool with no output schema is a high-burden case, and the description covers trigger, gating, side effects, and follow-up. The remaining gap is return-shape expectation — it references 'the confirmation' to share but doesn't say what the success response contains or what a refusal looks like.

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. The description still adds value by tying intent to parameters: the three fields to collect from the visitor and the precondition that final_price_confirmed must be an explicit confirmation of the exact total, not an inference. It says nothing about item_ids, preset_id, or visibility_interest beyond the schema, which keeps it at 4.

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 and resource ('Sends the itemized offer to the visitor's email') plus the concrete side effects (notify Marian, file into partners queue). It also explicitly distinguishes itself from the sibling set by claiming exclusivity: 'The ONLY tool that collects contact details.' An agent can identify this as the terminal/commit step 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?

Gives an explicit trigger and an explicit prohibition: collect name/email/company 'only when the visitor says they want the offer — never earlier.' It also sequences post-call behavior ('share the confirmation, then make ONE optional ask') and clarifies the ask is genuinely optional. This is when-to-use, when-not-to-use, and ordering all in one place.

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

All elc-partnership-builder 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