elc-partnership-builder

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

TableJSON Schema

Name	Required	Description
`context`	No	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.
`item_ids`	No	Optional: the basket composed so far, if any
`preset_id`	No	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.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 17, 2026

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."

Changed7 schema fields changedSep 11, 2026

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"
-]
```

Changed2 schema fields changedAug 26, 2026

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"
+]
```

Changed1 schema field changedAug 20, 2026

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"
+]

Changed2 schema fields changedAug 20, 2026

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"
+}

AddedAug 9, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds valuable context beyond annotations: it collects no contact details (the booking page handles everything), and that passing preset_id and item_ids produces a paste-ready booking note in the response. This lets the agent anticipate side effects and output behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is four sentences, each earning its place: first states purpose and distinction, second gives usage conditions, third discloses behavior, fourth explains parameter interaction. There is no fluff, and the core purpose is front-loaded before any secondary details.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool with zero required parameters, no output schema, and relatively low complexity, the description is fully adequate. It covers what the tool does, when to use it, that it does not collect contact details, and how parameters affect the response. An agent has everything needed to invoke it correctly.

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% for all three parameters, so the baseline is 3. The description enriches parameter meaning by explaining that preset_id and item_ids are only relevant if a package was composed, and that their presence changes the response to include a paste-ready booking note. This conditional behavior is not in the schema and raises the score above baseline.

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 clearly states the tool's purpose: a direct booking link for a 1:1 intro meeting with Marian Kamenistak, and explicitly distinguishes it from request_offer as the other legitimate ending. It uses a specific verb (book) and resource (intro meeting), making it unmistakable and well-differentiated from siblings.

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?

The description provides explicit when-to-use guidance: whenever the visitor hesitates, wants a human, or needs package tailoring beyond the catalog. It also names request_offer as the sibling alternative, but does not spell out the inverse conditions (when to prefer request_offer), so it stops short of a full when-not-to-use exclusion.

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 tools Inspect

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.

Book an intro meeting with Marian (the human ending)

Input Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources