Skip to main content
Glama

elc-partnership-builder

by io.engineeringleaders
OverviewDiscussionsAdmin

Book an intro meeting with Marian (the human ending)

book_intro_call
Read-onlyIdempotent

The second legitimate ending besides request_offer: a direct booking link for a 1:1 intro meeting with Marian Kamenistak, ELC's founder. Offer it whenever the visitor hesitates, wants a human, or the package needs tailoring beyond the catalog. No contact details collected here — the booking page handles everything. Pass preset_id and item_ids if a package was composed: the response then carries a paste-ready booking note, so the call starts from their numbers instead of from scratch.

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.
item_idsNoOptional: the basket composed so far, if any
preset_idNoOptional: the package composed so far, if any One of: free, team-seats, starter, pilot-meetup, hiring-meetup, intro-sprint, launch-audit, community-launch, launch-run, hiring, education, vital, visibility, story, product.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / preset_id / description
      Previous value: -"Optional: the package composed so far, if any 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: +"Optional: the package composed so far, if any 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: -"Optional: the package composed so far, if any One of: free, starter, leadership-pilot, pilot-meetup, launch-audit, community-launch, launch-run, hiring, education, vital, visibility, story, product."New value: +"Optional: the package composed so far, if any 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: -"Optional: the package composed so far, if any One of: free, starter, leadership-pilot, pilot-meetup, signature-meetup, launch-audit, community-launch, launch-run, hiring, education, vital, visibility, story, product."New value: +"Optional: the package composed so far, if any 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 / preset_id / description
      Previous value: -"Optional: the package composed so far, if any One of: free, starter, leadership-pilot, pilot-meetup, hiring, education, vital, visibility, story, product."New value: +"Optional: the package composed so far, if any One of: free, starter, leadership-pilot, pilot-meetup, signature-meetup, launch-audit, community-launch, launch-run, hiring, education, vital, visibility, story, product."
  5. Changed7 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."
    • addedInput schema / properties / item_ids / anyOf
      Added value: +[
+  {
+    "items": {
+      "type": "string"
+    },
+    "type": "array"
+  },
+  {
+    "type": "string"
+  }
+]
    • removedInput schema / properties / item_ids / items
      Removed value: -{
-  "type": "string"
-}
    • removedInput schema / properties / item_ids / type
      Removed value: -"array"
    • changedInput schema / properties / preset_id / description
      Previous value: -"Optional: the package composed so far, if any"New value: +"Optional: the package composed so far, if any 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"
-]
    • removedInput schema / required
      Removed value: -[
-  "context"
-]
  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"
+}
    • addedInput schema / required
      Added value: +[
+  "context"
+]
  7. 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"
+]
  8. Changed2 schema fields changed
    • addedInput schema / properties / item_ids
      Added value: +{
+  "description": "Optional: the basket composed so far, if any",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}
    • addedInput schema / properties / preset_id
      Added value: +{
+  "description": "Optional: the package composed so far, if any",
+  "enum": [
+    "free",
+    "leadership-pilot",
+    "pilot-meetup",
+    "team",
+    "vital",
+    "hiring",
+    "visibility",
+    "education",
+    "product",
+    "story"
+  ],
+  "type": "string"
+}
  9. Added

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 that no contact details are collected here and that the booking page owns that step, plus what the response contains ('paste-ready booking note'). That is real context beyond the annotations, though it doesn't state the concrete return shape.

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 the identity of the tool and its relationship to request_offer, then moves to usage triggers, then parameters — a sensible order with no filler. Dense but every clause adds something; slightly long for a three-optional-parameter tool.

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?

There is no output schema, so the description carries the return-value burden, and it does — the response yields a paste-ready booking note when preset_id/item_ids are supplied. Combined with the no-contact-details disclosure, an agent has enough to call this correctly; only the exact response shape is unspecified.

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 earns above-baseline credit by explaining *why* preset_id and item_ids matter: passing them makes the response carry a booking note so the call starts from the visitor's numbers. It also correctly implies all parameters are optional by saying 'if a package was composed.'

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 — booking a 1:1 intro call with the founder — and explicitly positions itself against a named sibling ('the second legitimate ending besides request_offer'). An agent can distinguish it from the other eleven tools 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 Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives concrete triggers: 'whenever the visitor hesitates, wants a human, or the package needs tailoring beyond the catalog,' and frames it as one of two endings alongside request_offer. It does not say when request_offer should win instead, which is the one selection decision left to inference.

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