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

TableJSON 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, starter, leadership-pilot, pilot-meetup, signature-meetup, 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 / 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."
  2. 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."
  3. 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"
-]
  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: -[
-  "name",
-  "email",
-  "company",
-  "final_price_confirmed",
-  "preset_id",
-  "item_ids"
-]New value: +[
+  "name",
+  "email",
+  "company",
+  "final_price_confirmed",
+  "preset_id",
+  "item_ids",
+  "context"
+]
  5. 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"
+]
  6. 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"
+]
  7. 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"
+]
  8. 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"
+]
  9. 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"
+}
  10. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations only declare the generic write/open-world/non-idempotent profile, so the description carries real weight: it discloses the visitor email send, the dual-channel notification to Marian, and queue-filing downstream effects. It leaves one meaningful trait unstated — that a repeated call (idempotentHint=false) would re-send and re-notify — which keeps it short of 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?

Purpose is front-loaded in the first sentence, followed by timing rules and the success follow-up. Slightly chatty in the closing script ('Optional means optional — the discount is already theirs'), though that line does do real work by preventing an over-pushy follow-up.

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?

Covers the call gate, the required confirmation state, and the post-call behavior for a 9-parameter write tool, and no output schema means return values need not be explained. It is complete enough to invoke correctly; only repeat-call consequences are unaddressed.

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 baseline is 3. The description confirms which fields are collected (name, work email, company) and frames the basket as 'the final basket', but adds no syntax, format, or constraint detail beyond what the property descriptions already provide.

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 ('Sends the itemized offer to the visitor's email') plus the full set of side effects (notify Marian, file into ELC's partners queue). The opening claim 'The ONLY tool that collects contact details' explicitly separates it from siblings like get_started or book_intro_call without requiring a schema comparison.

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 timing rule with an exclusion: 'Ask for name, work email and company only when the visitor says they want the offer — never earlier.' It also specifies the post-success flow (share confirmation, then ONE optional ask) and stresses the ask is optional, so the agent knows both when to call and what not to do.

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