elc-partnership-builder

Server Details

Build and price an ELC community partnership: match, customize, 12-month plan, 16% AI discount.

If you are the author of this connector, you can claim ownership by verifying the domain or GitHub account it belongs to. Claimed connector authors can inspect health checks, view analytics, and manage their listing.

Status: Healthy
Uptime: 100.0% over 76 days
Last Tested: 2026-11-01 15:22
Transport: Streamable HTTP · MCP 2025-11-25
URL
Repository: marian-kamenistak/elc-partnership-builder
GitHub Stars: 0
Server Listing: ELC Partnership Builder

TDQS

A4.4/5.0

Scored 2026-10-25 09:00 across 12 tools

Disambiguation4/5

The core sales flow tools (match_package, customize_package, design_journey, fit_to_budget, build_business_case, quote_reach_combo, request_offer) are each clearly distinct by function and the descriptions explain sequencing well. The one real collision is get_started vs get_more_tools, which both advertise themselves as the handler for greetings, liveness tests, and 'what can you do', returning the full menu — an agent could easily pick either. get_partnership_options vs get_reach_options are two 'START HERE' entry points but are differentiated by membership vs one-off scope.

Naming Consistency5/5

Every tool is snake_case and verb-first (book_, build_, customize_, design_, fit_, get_, match_, quote_, request_), with a predictable verb_noun shape throughout. No mixing of camelCase or noun-first names.

Tool Count5/5

Twelve tools is well within the ideal range and each one maps to a distinct step in the membership/one-off sales funnel. Nothing feels padded except arguably the redundant get_started/get_more_tools pair.

Completeness4/5

The funnel is covered end to end: discovery (get_partnership_options/get_reach_options), routing (match_package), composition (customize_package, fit_to_budget), justification (build_business_case, design_journey), pricing (quote_reach_combo), and closing (request_offer, book_intro_call). However there is no way to retrieve, reopen, or amend an offer/basket once submitted, and no tool to check the status of an existing partnership or booked call — dead ends for any follow-up conversation.

Available Tools

12 tools

book_intro_callBook an intro meeting with Marian (the human ending)A

Read-onlyIdempotent

Inspect

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.

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, team-seats, starter, pilot-meetup, hiring-meetup, intro-sprint, launch-audit, community-launch, launch-run, hiring, education, vital, visibility, story, product.

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.

build_business_caseCompute the ROI case and a forwardable approval memoA

Read-onlyIdempotent

Inspect

Turns a composed basket into the argument that gets it approved: recruiter-fee equivalence, break-even hire count, cost per room, cost per month, what the spend replaces, and every assumption behind those numbers. Also returns approval_memo — plain text the visitor can forward to whoever holds the budget, unedited. Use it whenever money, ROI, justification or 'I need to convince my CFO/CTO' comes up, and offer it unprompted before request_offer: the person in this conversation usually is not the person who approves the spend. Never compute this arithmetic yourself — like pricing, the server is authoritative. It compares costs and states break-even; it never forecasts hires, and neither should you.

Name	Required	Description
`kpis`	No	Optional: what has to move this year, in their words
`company`	No	Optional: company name, for the memo
`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	Required. The basket: item ids toggled ON
`preset_id`	No	Required. The package being justified One of: free, team-seats, starter, pilot-meetup, hiring-meetup, intro-sprint, launch-audit, community-launch, launch-run, hiring, education, vital, visibility, story, product.
`requester_name`	No	Optional: who is asking for approval, signed at the memo's foot
`open_senior_roles`	No	Optional: senior roles they need to fill in 12 months — sharpens the comparison into their numbers
`avg_first_year_salary`	No	Optional: average first-year salary in EUR for those roles; turns the generic fee band into their own

TDQS

A4.7/5.0

Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description still adds substantial behavior: it returns a forwardable plain-text `approval_memo`, the server is authoritative rather than the model, and it does comparative break-even only and never forecasts hires. These are real boundaries the annotations cannot express.

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?

Three sentences, purpose front-loaded, with the output enumeration, the triggering conditions, and the never-do-this-yourself constraint each earning their place. No filler or repetition.

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?

With eight parameters, no output schema, and no nested objects, the description supplies what's needed: what it returns (including the memo), what it does not do (forecast hires), and how it relates to `request_offer`. Nothing an agent needs to call it correctly is missing.

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 every parameter is already documented, and the description adds little per-parameter meaning beyond contextualizing `item_ids` as 'the basket' and noting the assumptions are surfaced. Baseline 3 is appropriate since the schema carries the parameter burden.

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 opens with a precise verb-plus-output framing ('Turns a composed basket into the argument that gets it approved') and then enumerates the exact outputs: recruiter-fee equivalence, break-even hire count, cost per room, cost per month, replacements, assumptions, plus `approval_memo`. An agent can distinguish this from `request_offer`, `fit_to_budget`, and `match_package` 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 concrete triggering conditions (money, ROI, justification, 'convince my CFO/CTO'), instructs proactive offering before `request_offer`, and warns the agent never to do the arithmetic itself. The only minor gap is no explicit when-not clause, but the 'before request_offer' ordering already covers the main sequencing decision.

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

customize_packageCustomize a package: toggle line items, recompute the totalA

Read-onlyIdempotent

Inspect

The conversational toggle board. Pass the preset and the item ids currently ON; returns the recomputed total (never trust your own arithmetic — this is the authoritative price), every selected item with its price, and what else this tier could add. Items marked foundation anchor the package; advise keeping them. Call again after every change the visitor asks for. Next: request_offer.

Name	Required	Description
`seats`	No	Seat-priced packages only (Team Seats `team-seats`, Team Circle `starter`): how many people they are enrolling. Both are priced per seat, so ALWAYS ask for a headcount before quoting — the bundle price is only the minimum-seat entry (Team Seats 5, Team Circle 3).
`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	Required. Item ids currently toggled ON (from match_package default_item_ids, plus/minus changes)
`preset_id`	No	Required. The package being customized One of: free, team-seats, starter, pilot-meetup, hiring-meetup, intro-sprint, launch-audit, community-launch, launch-run, hiring, education, vital, visibility, story, product.

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already declare read-only and idempotent, but the description's claim that the returned total is the authoritative price ("never trust your own arithmetic") is a genuinely useful behavioral constraint that prevents an agent from computing prices itself. It also discloses the return shape — total, selected items with prices, and available additions — plus the meaning of "foundation" items as anchored and advisory-to-keep.

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 core metaphor and the return contract, then the operational cadence, then the next step. The parenthetical about arithmetic is informal but earns its place as a behavioral warning; otherwise there is little waste.

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 no output schema, the description takes on the job of explaining return values and does so adequately (total, priced selections, addable items). The seat-pricing caveat lives in the schema rather than the description, which is acceptable given full coverage, but a one-line mention would make this self-sufficient.

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 schema already explains preset_id, item_ids, seats and context in detail. The description only restates that preset and item ids are passed and adds no syntax or edge-case detail, which is the expected baseline when the schema does the heavy lifting.

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?

Names a concrete action and resource: toggling line items on a package and returning a recomputed total. It also positions itself in the flow (takes preset and item ids, hands off to request_offer), so an agent can separate it from match_package and request_offer 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 Guidelines4/5

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

"Call again after every change the visitor asks for" and "Next: request_offer" give clear invocation cadence and a next step, and item_ids is implied to come from match_package. It stops short of explicit when-not-to-use guidance (e.g. always start with match_package first), which keeps it below a 5.

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

design_journeyLay out the 12-month membership journey for a basketA

Read-onlyIdempotent

Inspect

The moment the package becomes a year: deterministic month-by-month plan of what lands when, computed from the basket's own scheduling metadata (lead times, anchors like the April 2027 conference, spacing, and heavy-event collision rules). Returns placed months, the recurring-every-month layer, and anything unplaceable WITH its reason. The plan contains ONLY items in the basket — narrate around it, never add or move an event. Call after customize_package, before request_offer.

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	Required. The basket: item ids toggled ON
`preset_id`	No	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.
`start_month`	No	Required. First membership month, YYYY-MM (ask the visitor; default to the month after the current one)

TDQS

A4.8/5.0

Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description goes further: the plan is deterministic, items that cannot be placed are returned with their reason rather than silently dropped, and the output is constrained to basket items only. These are non-obvious behavioral traits an agent could not infer from the annotations.

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?

Four sentences, front-loaded with the core behavior and ending with the routing instruction. The open metaphor ('The moment the package becomes a year') costs a few words, but the remainder is dense and every sentence carries information.

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?

No output schema exists, so the description carries the return-value burden — and it does, naming the three result buckets including the failure case. For a read-only, deterministic planning tool with fully documented parameters, nothing an agent needs in order to call or interpret it is missing.

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 parameter documentation is already solid and the baseline is 3. The description adds real meaning beyond it by explaining that item_ids is a basket whose own metadata (lead times, anchors, spacing, collision rules) drives the computation, and that anchors like the April 2027 conference affect placement — context the schema does not convey.

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 — a deterministic month-by-month 12-month plan computed from the basket's own scheduling metadata. The 'Returns placed months, the recurring-every-month layer, and anything unplaceable WITH its reason' clause makes the output shape concrete, so it is clearly distinguishable from package-building siblings.

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?

Explicit sequencing: 'Call after customize_package, before request_offer', which places it precisely in the workflow relative to two named siblings. It also gives a downstream usage rule — narrate around the plan, never add or move an event — so the agent knows both when to call it and how to use the result.

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

fit_to_budgetCompose the best package for an exact budgetA

Read-onlyIdempotent

Inspect

Use when the visitor names a NUMBER rather than a band — 'we have 8,000 approved', 'can we do this for five thousand'. Returns a deterministic best-value composition under that ceiling: what fits, what was left out AND why, how much budget is unspent, and what the cheapest excluded item costs. Foundation items are kept first, then the remaining items cheapest-first so the budget buys as much as possible. Priced against the AI-channel figure by default, since that is what they would actually pay. Never hand-pick a basket yourself when a budget is stated — this tool is the authoritative composition, the same way customize_package is the authoritative total.

Name	Required	Description
`budget`	No	Required. The visitor's ceiling in EUR, as a number (8000, not '8K')
`against`	No	Price the budget against the list price. 'discounted' equals list since the AI channel carries no discount (2026-10-05) One of: discounted, list.
`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.
`must_have`	No	Optional: item ids the visitor explicitly asked for; kept first if they fit
`preset_id`	No	Required. The package to trim to budget (from match_package) One of: free, team-seats, starter, pilot-meetup, hiring-meetup, intro-sprint, launch-audit, community-launch, launch-run, hiring, education, vital, visibility, story, product.

TDQS

A4.8/5.0

Behavior5/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive), but the description adds what they cannot: deterministic output, the allocation algorithm (foundation items first, then cheapest-first), which pricing channel is the default and why, and exactly which derived facts are returned (what was excluded and why, unspent budget, cheapest excluded item). This is substantial context beyond structured fields.

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 trigger condition, then the return shape, then the algorithm, then the routing rule — a sensible order. The middle sentence is dense and packs several return fields into one clause, but every sentence carries information an agent needs.

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?

Despite having no output schema, the description enumerates the meaningful parts of the result, so an agent knows what it will get back. Combined with the determinism guarantee and the pricing note, an agent can call this correctly and interpret the response without further context.

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 would be 3; the description earns above that by explaining the default value of 'against' (the AI-channel figure, because that is what the visitor actually pays) and the ordering semantics of must_have ('kept first if they fit'). It adds meaning rather than restating the schema, though it does not touch budget format or preset_id.

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 — compose the best package for an exact budget — and names the trigger condition (a number, not a band) that separates it from band-based siblings like match_package. The contrast with customize_package makes the division of labour unambiguous.

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?

Explicit when-to-use ('visitor names a NUMBER rather than a band') with quoted example phrasings, plus an explicit prohibition ('Never hand-pick a basket yourself when a budget is stated') and a named alternative for the total-price case. Nothing is left to inference.

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

get_more_toolsReport a missing capability — also answers a bare hello/liveness pingA

Read-onlyIdempotent

Inspect

Check for additional tools whenever your task might benefit from specialized capabilities, even if existing tools could work as a fallback. Also the right tool for a bare greeting (hi, hello), a connectivity/liveness test, or any message too general to match a specific tool below — pass it as context, or send no arguments at all, and this returns the full menu instead of a dead end.

Name	Required	Description	Default
`context`	No	A description of your goal and what kind of tool would help accomplish it, OR a plain greeting/liveness ping like 'hi' or 'test'. Omit it for the menu.

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already provide readOnlyHint and idempotentHint. The description adds behavioral context: it returns the full menu instead of a dead end, and works as a liveness ping. This is useful beyond the annotations, though it doesn't describe details like response format or pagination, which is acceptable for a simple tool.

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?

The description is a bit longer than strictly necessary but every sentence serves a purpose: it covers the primary use, the fallback use, and the parameter behavior. The main use case is front-loaded, and there's no filler or redundancy.

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?

Given the single optional parameter, no output schema, and rich annotations, the description fully covers how to invoke the tool (with or without context), what it returns (full menu), and when to use it. Nothing an agent needs to call it correctly is missing.

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 explicitly explains the 'context' parameter, including the omit-for-menu behavior. The description reiterates this but adds no new semantic meaning beyond what the schema already provides, so it meets the baseline for high schema coverage.

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 dual purpose: finding additional tools for specialized capabilities and handling bare greetings/liveness pings. It distinguishes itself from the listed siblings by being the catch-all fallback tool, saying 'any message too general to match a specific tool below' – a specific verb+resource with clear differentiation.

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?

Explicitly states when to use: when the task might benefit from specialized capabilities even if fallback exists, and for bare greetings or general messages. It also defines the exclusion condition ('too general to match a specific tool'), and explains the parameter use and omission behavior, giving the agent actionable routing guidance.

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

get_partnership_optionsHow ELC company membership works + the two qualifying questionsA

Read-onlyIdempotent

Inspect

START HERE for any company considering an ELC membership (personas: HR, CTO, employer branding). Returns how company membership works, real community reach figures, and the two qualifying questions with their valid answers. Companies only — individuals seeking a mentor for themselves get pointed to /mentor/ instead. After the visitor answers both questions, call match_package. Partner packages and tickets for the ELC Conference 2027 day are a separate offer with their own MCP server: https://mcp.elc-conference.io/mcp

Name	Required	Description	Default
`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.

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare this as a safe, idempotent, non-destructive, closed-world read, and the description respects that framing while adding useful behavioral context: it is the entry point of a multi-step flow and the next call is match_package. It does not describe pagination, latency, or caching, but for a static informational read tool that gap is minor.

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 critical routing instruction ('START HERE') and each sentence carries distinct information: purpose, exclusions, next step, and sibling offer. It is slightly dense with parenthetical asides (personas, URL) but no sentence is wasted.

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?

No output schema exists, but the description enumerates what is returned (membership mechanics, community reach figures, the two qualifying questions with valid answers) and where the flow continues. For a zero-required-parameter orientation tool, an agent has everything needed to call it and act on the result.

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?

There is a single optional parameter and schema coverage is 100%, so the schema already explains that context is optional intent-logging that never changes the answer. The description adds no additional parameter meaning, so the baseline of 3 for high schema coverage 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?

Names a specific verb and resource ('START HERE' orientation tool returning how ELC company membership works, reach figures, and qualifying questions). It explicitly distinguishes itself from siblings by routing elsewhere: individuals to /mentor/, conference tickets to a separate MCP server, and post-qualification flow to match_package.

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?

Explicitly states when to use it ('START HERE for any company considering an ELC membership'), its target personas, the exclusion ('Companies only — individuals seeking a mentor... get pointed to /mentor/'), and the sequencing into match_package. The alternative offers and their separate endpoint are named too, leaving nothing to inference.

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

get_reach_optionsOne-offs: single items a company buys once, with pricesA

Read-onlyIdempotent

Inspect

START HERE when a company wants ONE thing once, not a year-long membership: a classified (30 words and a link, tools and events only) or a dedicated send in the Leaders' Brief newsletter, a meetup hosted in their office, a speaker slot or the coached speaker programme, a conference main-stage talk, a podcast episode, a decision-maker dinner, a community survey, a job board listing. Returns every one-off with its price, lead time, examples and real reach figures, the combo discount rule, the 90-day credit against a membership, and what is not for sale. Two or more things across a year is a membership conversation: hand over to get_partnership_options. Next: quote_reach_combo once items are picked.

Name	Required	Description	Default
`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.

TDQS

A4.6/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 substantive behavioral context beyond that: it discloses the payload contents (price, lead time, examples, real reach figures, combo discount rule, 90-day credit) and even a boundary ('what is not for sale'), which helps the agent set expectations. It stops short of addressing staleness or guarantees on the figures.

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 'START HERE' and the routing decision, with the item enumeration in the middle and the next-step hand-off last. The long comma list of purchasable items is dense but each entry gives the agent concrete matching surface; slightly compressed formatting would read better.

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?

There is no output schema, so the description must explain the return values, and it does so explicitly (prices, lead times, examples, reach figures, discount rule, credit terms, exclusions). Combined with the routing guidance, an agent has everything needed to call this correctly and act on the result.

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?

Only one optional parameter ('context'), documented at 100% schema coverage, and the schema already says it is recorded as intent and never changes the answer. Zero-required-parameter tools earn a high baseline here; the description adds nothing about the param but nothing is missing.

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?

Names a specific resource (one-off items) with a concrete enumeration of what's included (classified, newsletter send, meetup, speaker slot, podcast, dinner, survey, job board), and explicitly distinguishes itself from the membership path. An agent can tell exactly what this tool returns 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?

Explicit trigger ('START HERE when a company wants ONE thing once'), explicit exclusion with the sibling to hand over to ('Two or more things across a year is a membership conversation: hand over to get_partnership_options'), and an explicit next step ('quote_reach_combo once items are picked'). Full when/when-not/next routing.

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

get_startedStart here — what can this MCP server do?A

Read-onlyIdempotent

Inspect

Call this for a greeting (hi, hello), a connectivity/liveness test, 'what can you do', or any message too general to match a specific tool below. Returns the full menu of real questions this server answers, each mapped to the tool name that answers it. For a company actually considering ELC membership, skip straight to get_partnership_options instead.

Name	Required	Description	Default
`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.

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the bar is lower. The description adds useful context by disclosing the return shape (a menu of questions mapped to answering tools) and the routing behavior, though it says nothing about output size, pagination, or how the menu is structured beyond 'mapped to tool name'.

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?

Three sentences, front-loaded with the call triggers, then the return value, then the sibling routing. No filler; each sentence carries distinct information.

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?

There is no output schema, so the description appropriately compensates by explaining what the tool returns and how the result is organized. For a zero-required-parameter routing tool, nothing an agent needs to invoke it correctly is missing.

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 single optional 'context' parameter is fully documented in the schema, including the note that it never changes the answer. The description adds no parameter-level meaning, so the baseline of 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?

The description states a specific function — an onboarding/router tool that returns a menu of real questions mapped to the tool names that answer them — and clearly distinguishes itself from siblings by naming get_partnership_options as the alternate route. An agent can tell exactly what this tool is for 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?

Explicit triggers are enumerated (greeting, hello, connectivity/liveness test, 'what can you do', any too-general message), and an explicit exclusion routes ELC membership prospects to get_partnership_options. This is close to ideal when/when-not guidance.

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

match_packageMatch a membership package to a goal and budgetA

Read-onlyIdempotent

Inspect

Resolves goal + budget through ELC's own routing matrix — the same one the website uses — and returns the matched package(s) with real prices and their default line items. Map free-text answers to the closest valid id; on bad input the error lists the valid ids, re-ask rather than guessing. Next: customize_package to toggle line items, or request_offer to send it as-is.

Name	Required	Description
`goal`	No	Required. One of the goal ids from get_partnership_options question_1
`budget`	No	Required. One of the budget ids from get_partnership_options question_2
`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.

TDQS

A4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description adds real behavioral context beyond that: the matrix is the same one the website uses, bad input produces an error listing valid ids, and the optional context value is recorded as intent but never changes the answer.

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?

Three sentences, front-loaded with what the tool does and its output, then error handling, then next steps. No filler, no restatement of the name or title.

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?

No output schema exists, so the description carries the return-value burden and does explain that packages, real prices and default line items come back. It covers error behavior and downstream chaining. Minor gaps remain on whether multiple matches are common and what happens if the matrix yields no match.

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 goal, budget and context are already documented, including that context never affects the answer. The description only adds the fuzzy-mapping guidance ('map free-text answers to the closest valid id'), which refines usage rather than the parameters themselves. Baseline 3 applies when the schema does the heavy lifting.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Specific verb and resource: it resolves goal+budget through a named routing matrix and returns matched packages with real prices and default line items. That is far more concrete than the title alone. It does not, however, distinguish itself from the sibling fit_to_budget, which plausibly does related budget matching, so an agent still has to infer which of the two to call.

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 invocation guidance: map free-text answers to the closest valid id, and on error re-ask rather than guess. It also routes forward explicitly to customize_package (to toggle line items) and request_offer (to send as-is). It stops short of naming when NOT to use this tool in favor of fit_to_budget or design_journey.

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

quote_reach_comboPrice a one-off basket (authoritative total with the combo discount)A

Read-onlyIdempotent

Inspect

Pass the one-off ids the visitor picked; returns each item's price, the list total, the combo discount by item count (job board listings never count), and the final total. For the speaker programme pass speaker_rungs to price a subset of the ladder (Stage always included); omit it for the full programme at the bundle price. This is the only arithmetic that counts — never add prices yourself. The AI-channel percentage does not apply to one-offs. Next: book_intro_call to lock the date, or get_partnership_options if the basket is starting to look like a year.

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.
`oneoff_ids`	No	Required. One-off ids from get_reach_options One or more of: meetup-hosted, speaker-development, conference-main-stage, newsletter-dedicated, newsletter-classified, dinner, podcast-episode, survey, job-listing.
`speaker_rungs`	No	Speaker programme rung ids (stage, story, coach, amplify, beyond) to price instead of the full programme; stage is always included

TDQS

A4.6/5.0

Behavior5/5

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

Annotations already establish read-only, idempotent, non-destructive behavior, so the description's job is to add business logic — and it does: the combo discount keys off item count, job-board listings never count toward it, and the AI-channel percentage is excluded from one-offs. These are non-obvious rules an agent could not derive from annotations or schema.

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?

Dense and front-loaded: the return contract comes first, then the speaker-programme branch, then the authoritative-arithmetic warning. The trailing 'Next:' routing is useful but slightly beyond the tool's own purpose, keeping it from a 5.

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?

There is no output schema, so the description must carry the return contract, and it does — it lists every value returned. Combined with the discount rules and the speaker-programme branch, an agent has everything it needs to call this correctly without follow-up.

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% and all parameters are documented, so the baseline is 3. The description adds genuine meaning beyond the schema for speaker_rungs — that Stage is always included and that omitting the parameter prices the full ladder at the bundle price — pushing it to 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 ('price a one-off basket') and immediately enumerates the outputs: per-item price, list total, combo discount, final total. It also carves out the speaker-programme case, so an agent can tell it apart from get_reach_options (which lists options) and match_package (which matches packages).

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 an explicit directive ('never add prices yourself') and precise branching for speaker_rungs: pass it to price a subset, omit it for the full programme at the bundle price. It stops short of stating when to prefer match_package or fit_to_budget over this tool, so 4 rather than 5.

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

request_offerSend the composed offer to ELCAInspect

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.

Name	Required	Description
`kpis`	No	Optional: what they need to move this year, in their words
`name`	No	Required. Visitor's full name
`email`	No	Required. Work email the offer goes to
`company`	No	Required. Company name
`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	Required. The final basket: item ids toggled ON
`preset_id`	No	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.
`visibility_interest`	No	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.
`final_price_confirmed`	No	Required. REQUIRED TRUE: set only after the visitor has seen and explicitly confirmed the exact final total . Sending without this confirmation is refused.

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.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

7 tool updatesOct 25, 2026

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

Changedbuild_business_case1 field changed

changedInput schema / properties / preset_id / description

Previous value: -"Required. The package being justified 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. The package being justified One of: free, team-seats, starter, pilot-meetup, hiring-meetup, intro-sprint, launch-audit, community-launch, launch-run, hiring, education, vital, visibility, story, product."

Changedcustomize_package2 fields changed

changedInput schema / properties / preset_id / description

Previous value: -"Required. The package being customized 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. The package being customized One of: free, team-seats, starter, pilot-meetup, hiring-meetup, intro-sprint, launch-audit, community-launch, launch-run, hiring, education, vital, visibility, story, product."

changedInput schema / properties / seats / description

Previous value: -"Starter only: how many people they are enrolling. Starter is priced per seat with volume bands, so ALWAYS ask for a headcount before quoting it — the bundle price is only the 3-seat entry."New value: +"Seat-priced packages only (Team Seats `team-seats`, Team Circle `starter`): how many people they are enrolling. Both are priced per seat, so ALWAYS ask for a headcount before quoting — the bundle price is only the minimum-seat entry (Team Seats 5, Team Circle 3)."

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

Changedfit_to_budget1 field changed

changedInput schema / properties / preset_id / description

Previous value: -"Required. The package to trim to budget (from match_package) 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. The package to trim to budget (from match_package) One of: free, team-seats, starter, pilot-meetup, hiring-meetup, intro-sprint, launch-audit, community-launch, launch-run, hiring, education, vital, visibility, story, product."

Changedquote_reach_combo1 field changed

changedInput schema / properties / oneoff_ids / description

Previous value: -"Required. One-off ids from get_reach_options One or more of: meetup-hosted, speaker-development, conference-main-stage, newsletter-dedicated, newsletter-section, dinner, podcast-episode, meetup-presence, survey, job-listing."New value: +"Required. One-off ids from get_reach_options One or more of: meetup-hosted, speaker-development, conference-main-stage, newsletter-dedicated, newsletter-classified, dinner, podcast-episode, survey, job-listing."

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

6 tool updatesOct 20, 2026

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

Changedbuild_business_case1 field changed

changedInput schema / properties / preset_id / description

Previous value: -"Required. The package being justified One of: free, starter, leadership-pilot, pilot-meetup, launch-audit, community-launch, launch-run, hiring, education, vital, visibility, story, product."New value: +"Required. The package being justified One of: free, starter, leadership-pilot, pilot-meetup, hiring-meetup, intro-sprint, launch-audit, community-launch, launch-run, hiring, education, vital, visibility, story, product."

Changedcustomize_package1 field changed

changedInput schema / properties / preset_id / description

Previous value: -"Required. The package being customized One of: free, starter, leadership-pilot, pilot-meetup, launch-audit, community-launch, launch-run, hiring, education, vital, visibility, story, product."New value: +"Required. The package being customized One of: free, starter, leadership-pilot, pilot-meetup, hiring-meetup, intro-sprint, launch-audit, community-launch, launch-run, hiring, education, vital, visibility, story, product."

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

Changedfit_to_budget1 field changed

changedInput schema / properties / preset_id / description

Previous value: -"Required. The package to trim to budget (from match_package) One of: free, starter, leadership-pilot, pilot-meetup, launch-audit, community-launch, launch-run, hiring, education, vital, visibility, story, product."New value: +"Required. The package to trim to budget (from match_package) One of: free, starter, leadership-pilot, pilot-meetup, hiring-meetup, intro-sprint, launch-audit, community-launch, launch-run, hiring, education, vital, visibility, story, product."

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

7 tool updatesOct 20, 2026

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

Changedbuild_business_case1 field changed

changedInput schema / properties / preset_id / description

Previous value: -"Required. The package being justified 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. The package being justified One of: free, starter, leadership-pilot, pilot-meetup, launch-audit, community-launch, launch-run, hiring, education, vital, visibility, story, product."

Changedcustomize_package1 field changed

changedInput schema / properties / preset_id / description

Previous value: -"Required. The package being customized 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. The package being customized One of: free, starter, leadership-pilot, pilot-meetup, launch-audit, community-launch, launch-run, hiring, education, vital, visibility, story, product."

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

Changedfit_to_budget1 field changed

changedInput schema / properties / preset_id / description

Previous value: -"Required. The package to trim to budget (from match_package) 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. The package to trim to budget (from match_package) One of: free, starter, leadership-pilot, pilot-meetup, launch-audit, community-launch, launch-run, hiring, education, vital, visibility, story, product."

Changedquote_reach_combo1 field changed

addedInput schema / properties / speaker_rungs

Added value: +{
+  "anyOf": [
+    {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    {
+      "type": "string"
+    }
+  ],
+  "description": "Speaker programme rung ids (stage, story, coach, amplify, beyond) to price instead of the full programme; stage is always included"
+}

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

2 tool updatesOct 5, 2026

Changedfit_to_budget1 field changed

changedInput schema / properties / against / description

Previous value: -"Price the budget against the AI-channel figure (default) or the list price One of: discounted, list."New value: +"Price the budget against the list price. 'discounted' equals list since the AI channel carries no discount (2026-10-05) One of: discounted, list."

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

1 tool updateOct 5, 2026

Changedquote_reach_combo1 field changed

changedInput schema / properties / oneoff_ids / description

Previous value: -"Required. One-off ids from get_reach_options One or more of: meetup-hosted, meetup-presence, newsletter-section, newsletter-dedicated, podcast-episode, dinner, survey, demo-session, webinar, linkedin-post, job-listing, speaker-development."New value: +"Required. One-off ids from get_reach_options One or more of: meetup-hosted, speaker-development, conference-main-stage, newsletter-dedicated, newsletter-section, dinner, podcast-episode, meetup-presence, survey, job-listing."

1 tool updateOct 5, 2026

Changedquote_reach_combo1 field changed

changedInput schema / properties / oneoff_ids / description

Previous value: -"Required. One-off ids from get_reach_options One or more of: meetup-presence, newsletter-section, newsletter-dedicated, meetup-hosted, meetup-signature, podcast-episode, dinner, survey, demo-session, webinar, linkedin-post, job-listing, speaker-development."New value: +"Required. One-off ids from get_reach_options One or more of: meetup-hosted, meetup-presence, newsletter-section, newsletter-dedicated, podcast-episode, dinner, survey, demo-session, webinar, linkedin-post, job-listing, speaker-development."

1 tool updateSep 24, 2026

Changedquote_reach_combo1 field changed

changedInput schema / properties / oneoff_ids / description

Previous value: -"Required. One-off ids from get_reach_options One or more of: meetup-presence, newsletter-section, newsletter-dedicated, meetup-hosted, meetup-signature, podcast-episode, dinner, survey, demo-session, linkedin-post, job-listing, speaker-development."New value: +"Required. One-off ids from get_reach_options One or more of: meetup-presence, newsletter-section, newsletter-dedicated, meetup-hosted, meetup-signature, podcast-episode, dinner, survey, demo-session, webinar, linkedin-post, job-listing, speaker-development."

1 tool updateSep 21, 2026

Changedquote_reach_combo1 field changed

changedInput schema / properties / oneoff_ids / description

Previous value: -"Required. One-off ids from get_reach_options One or more of: meetup-presence, newsletter-section, newsletter-dedicated, meetup-hosted, meetup-signature, podcast-episode, dinner, survey, demo-session, linkedin-post, job-listing."New value: +"Required. One-off ids from get_reach_options One or more of: meetup-presence, newsletter-section, newsletter-dedicated, meetup-hosted, meetup-signature, podcast-episode, dinner, survey, demo-session, linkedin-post, job-listing, speaker-development."

7 tool updatesSep 17, 2026

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

Changedbuild_business_case1 field changed

changedInput schema / properties / preset_id / description

Previous value: -"Required. The package being justified One of: free, starter, leadership-pilot, pilot-meetup, hiring, education, vital, visibility, story, product."New value: +"Required. The package being justified One of: free, starter, leadership-pilot, pilot-meetup, signature-meetup, launch-audit, community-launch, launch-run, hiring, education, vital, visibility, story, product."

Changedcustomize_package1 field changed

changedInput schema / properties / preset_id / description

Previous value: -"Required. The package being customized One of: free, starter, leadership-pilot, pilot-meetup, hiring, education, vital, visibility, story, product."New value: +"Required. The package being customized One of: free, starter, leadership-pilot, pilot-meetup, signature-meetup, launch-audit, community-launch, launch-run, hiring, education, vital, visibility, story, product."

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

Changedfit_to_budget1 field changed

changedInput schema / properties / preset_id / description

Previous value: -"Required. The package to trim to budget (from match_package) One of: free, starter, leadership-pilot, pilot-meetup, hiring, education, vital, visibility, story, product."New value: +"Required. The package to trim to budget (from match_package) One of: free, starter, leadership-pilot, pilot-meetup, signature-meetup, launch-audit, community-launch, launch-run, hiring, education, vital, visibility, story, product."

Changedquote_reach_combo1 field changed

changedInput schema / properties / oneoff_ids / description

Previous value: -"Required. One-off ids from get_reach_options One or more of: meetup-presence, newsletter-section, newsletter-dedicated, meetup-hosted, podcast-episode, dinner, survey, demo-session, linkedin-post, job-listing."New value: +"Required. One-off ids from get_reach_options One or more of: meetup-presence, newsletter-section, newsletter-dedicated, meetup-hosted, meetup-signature, podcast-episode, dinner, survey, demo-session, linkedin-post, job-listing."

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

11 tool updatesSep 11, 2026

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

Changedbuild_business_case12 fields changed

addedInput schema / properties / avg_first_year_salary / anyOf

Added value: +[
+  {
+    "type": "number"
+  },
+  {
+    "type": "string"
+  }
+]

removedInput schema / properties / avg_first_year_salary / type
```
Removed value: -"number"
```

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

changedInput schema / properties / item_ids / description

Previous value: -"The basket: item ids toggled ON"New value: +"Required. The basket: item ids toggled ON"

removedInput schema / properties / item_ids / items
```
Removed value: -{
-  "type": "string"
-}
```
removedInput schema / properties / item_ids / type
```
Removed value: -"array"
```

addedInput schema / properties / open_senior_roles / anyOf

Added value: +[
+  {
+    "type": "number"
+  },
+  {
+    "type": "string"
+  }
+]

removedInput schema / properties / open_senior_roles / type
```
Removed value: -"number"
```

changedInput schema / properties / preset_id / description

Previous value: -"The package being justified"New value: +"Required. The package being justified 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: -[
-  "preset_id",
-  "item_ids",
-  "context"
-]

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

changedInput schema / properties / item_ids / description

Previous value: -"Item ids currently toggled ON (from match_package default_item_ids, plus/minus changes)"New value: +"Required. Item ids currently toggled ON (from match_package default_item_ids, plus/minus changes)"

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: -"The package being customized"New value: +"Required. The package being customized 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"
-]

addedInput schema / properties / seats / anyOf

Added value: +[
+  {
+    "type": "number"
+  },
+  {
+    "type": "string"
+  }
+]

removedInput schema / properties / seats / type
```
Removed value: -"number"
```

removedInput schema / required

Removed value: -[
-  "preset_id",
-  "item_ids",
-  "context"
-]

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

changedInput schema / properties / item_ids / description

Previous value: -"The basket: item ids toggled ON"New value: +"Required. The basket: item ids toggled ON"

removedInput schema / properties / item_ids / items
```
Removed value: -{
-  "type": "string"
-}
```
removedInput schema / properties / item_ids / type
```
Removed value: -"array"
```

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 / start_month / description

Previous value: -"First membership month, YYYY-MM (ask the visitor; default to the month after the current one)"New value: +"Required. First membership month, YYYY-MM (ask the visitor; default to the month after the current one)"

removedInput schema / required

Removed value: -[
-  "preset_id",
-  "item_ids",
-  "start_month",
-  "context"
-]

Changedfit_to_budget12 fields changed

changedInput schema / properties / against / description

Previous value: -"Price the budget against the AI-channel figure (default) or the list price"New value: +"Price the budget against the AI-channel figure (default) or the list price One of: discounted, list."

removedInput schema / properties / against / enum

Removed value: -[
-  "discounted",
-  "list"
-]

addedInput schema / properties / budget / anyOf

Added value: +[
+  {
+    "type": "number"
+  },
+  {
+    "type": "string"
+  }
+]

changedInput schema / properties / budget / description

Previous value: -"The visitor's ceiling in EUR, as a number (8000, not '8K')"New value: +"Required. The visitor's ceiling in EUR, as a number (8000, not '8K')"

removedInput schema / properties / budget / type
```
Removed value: -"number"
```

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 / must_have / anyOf

Added value: +[
+  {
+    "items": {
+      "type": "string"
+    },
+    "type": "array"
+  },
+  {
+    "type": "string"
+  }
+]

removedInput schema / properties / must_have / items
```
Removed value: -{
-  "type": "string"
-}
```
removedInput schema / properties / must_have / type
```
Removed value: -"array"
```

changedInput schema / properties / preset_id / description

Previous value: -"The package to trim to budget (from match_package)"New value: +"Required. The package to trim to budget (from match_package) 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: -[
-  "preset_id",
-  "budget",
-  "context"
-]

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

removedInput schema / required
```
Removed value: -[
-  "context"
-]
```

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

removedInput schema / required
```
Removed value: -[
-  "context"
-]
```

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

removedInput schema / required
```
Removed value: -[
-  "context"
-]
```

Changedmatch_package4 fields changed

changedInput schema / properties / budget / description

Previous value: -"One of the budget ids from get_partnership_options question_2"New value: +"Required. One of the budget ids from get_partnership_options question_2"

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: -"One of the goal ids from get_partnership_options question_1"New value: +"Required. One of the goal ids from get_partnership_options question_1"

removedInput schema / required

Removed value: -[
-  "goal",
-  "budget",
-  "context"
-]

Changedquote_reach_combo7 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 / oneoff_ids / anyOf

Added value: +[
+  {
+    "items": {
+      "type": "string"
+    },
+    "type": "array"
+  },
+  {
+    "type": "string"
+  }
+]

changedInput schema / properties / oneoff_ids / description

Previous value: -"One-off ids from get_reach_options"New value: +"Required. One-off ids from get_reach_options One or more of: meetup-presence, newsletter-section, newsletter-dedicated, meetup-hosted, podcast-episode, dinner, survey, demo-session, linkedin-post, job-listing."

removedInput schema / properties / oneoff_ids / items

Removed value: -{
-  "enum": [
-    "meetup-presence",
-    "newsletter-section",
-    "newsletter-dedicated",
-    "meetup-hosted",
-    "podcast-episode",
-    "dinner",
-    "survey",
-    "demo-session",
-    "linkedin-post",
-    "job-listing"
-  ],
-  "type": "string"
-}

removedInput schema / properties / oneoff_ids / minItems
```
Removed value: -1
```
removedInput schema / properties / oneoff_ids / type
```
Removed value: -"array"
```

removedInput schema / required

Removed value: -[
-  "oneoff_ids",
-  "context"
-]

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

1 tool updateSep 9, 2026

Changedget_more_tools2 fields changed

changedInput schema / properties / context / description

Previous value: -"A description of your goal and what kind of tool would help accomplish it, OR a plain greeting/liveness ping like 'hi' or 'test'."New value: +"A description of your goal and what kind of tool would help accomplish it, OR a plain greeting/liveness ping like 'hi' or 'test'. Omit it for the menu."

removedInput schema / required
```
Removed value: -[
-  "context"
-]
```

1 tool updateSep 9, 2026

Changedquote_reach_combo1 field changed

changedInput schema / properties / oneoff_ids / items / enum

Previous value: -[
-  "newsletter-section",
-  "newsletter-dedicated",
-  "meetup-hosted",
-  "podcast-episode",
-  "dinner",
-  "survey",
-  "demo-session",
-  "linkedin-post",
-  "job-listing"
-]New value: +[
+  "meetup-presence",
+  "newsletter-section",
+  "newsletter-dedicated",
+  "meetup-hosted",
+  "podcast-episode",
+  "dinner",
+  "survey",
+  "demo-session",
+  "linkedin-post",
+  "job-listing"
+]

1 tool updateSep 4, 2026

Changedget_more_tools2 fields changed

addedInput schema / $schema

Added value: +"http://json-schema.org/draft-07/schema#"

changedInput schema / properties / context / description

Previous value: -"A description of your goal and what kind of tool would help accomplish it."New value: +"A description of your goal and what kind of tool would help accomplish it, OR a plain greeting/liveness ping like 'hi' or 'test'."

2 tool updatesSep 3, 2026
- Addedget_reach_options
- Addedquote_reach_combo
1 tool updateSep 3, 2026
- Addedget_started

9 tool updatesAug 26, 2026

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

Changedbuild_business_case2 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: -[
-  "preset_id",
-  "item_ids"
-]New value: +[
+  "preset_id",
+  "item_ids",
+  "context"
+]

Changedcustomize_package2 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: -[
-  "preset_id",
-  "item_ids"
-]New value: +[
+  "preset_id",
+  "item_ids",
+  "context"
+]

Changeddesign_journey2 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: -[
-  "preset_id",
-  "item_ids",
-  "start_month"
-]New value: +[
+  "preset_id",
+  "item_ids",
+  "start_month",
+  "context"
+]

Changedfit_to_budget2 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: -[
-  "preset_id",
-  "budget"
-]New value: +[
+  "preset_id",
+  "budget",
+  "context"
+]

Addedget_more_tools

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

Changedmatch_package2 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",
-  "budget"
-]New value: +[
+  "goal",
+  "budget",
+  "context"
+]

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

1 tool updateAug 21, 2026

Changeddesign_journey1 field changed

changedInput schema / properties / start_month / description

Previous value: -"First partnership month, YYYY-MM (ask the visitor; default to the month after the current one)"New value: +"First membership month, YYYY-MM (ask the visitor; default to the month after the current one)"

6 tool updatesAug 20, 2026

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

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

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

changedInput schema / properties / seats / description

Previous value: -"Team only: how many people they are enrolling. Team is priced per seat with volume bands, so ALWAYS ask for a headcount before quoting it — the bundle price is only the 3-seat entry."New value: +"Starter only: how many people they are enrolling. Starter is priced per seat with volume bands, so ALWAYS ask for a headcount before quoting it — the bundle price is only the 3-seat entry."

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

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

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

4 tool updatesAug 20, 2026

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

Addedbuild_business_case

Changedcustomize_package1 field changed

addedInput schema / properties / seats

Added value: +{
+  "description": "Team only: how many people they are enrolling. Team is priced per seat with volume bands, so ALWAYS ask for a headcount before quoting it — the bundle price is only the 3-seat entry.",
+  "type": "number"
+}

Addedfit_to_budget

Related MCP Connectors

elc-toolkit A
io.engineeringleaders
Leadership-ratio benchmark, partnership ROI builder, community-launch readiness test. ELC data.
Research & Data Product Management
61
https://www.engineeringleaders.io/mcp
elc-trade A
io.engineeringleaders
Score a meetup topic, place a speaker on the right stage, price community reach. ELC data.
Product Management Research & Data
91
https://www.engineeringleaders.io/mcp/trade
ELC Conference 2027: tickets, perks, partnerships A
io.github.marian-kamenistak
ELC Conference 2027, Prague: tickets, attendee perks and partnership quotes from your AI assistant.
E-commerce & Retail App Automation Travel & Transportation
192
https://mcp.elc-conference.io/mcp
marz-greta-lock-network B
dev.eqbuilder
EQ scoring plus a read-only Storelayer matcher and guarded self-install; no website credentials
Databases Data Platforms
81
https://eqbuilder.dev/api/mcp

Related MCP Servers

Cohort
Education & Learning Tools Knowledge & Memory RAG Systems
LAHutchins91
A
license
Not graded
quality
F
maintenance
Approved curriculum for coaches, connected to AI assistants over MCP. A 14-day trial, then Pro. The price is only at checkout.
Updated a month ago (2026-10-05 02:36 UTC)
6 npm
MIT
Faroz MCP
Education & Learning Tools Games & Gamification Calendar Management
Akramjon-koder
A
license
Not graded
quality
B
maintenance
Connects AI assistants to a children's education platform so teachers, parents and content authors can create courses, lessons and interactive exercises, manage lesson calendars, review and grade homework, and track student progress through natural conversation. It also supports building educational games, media libraries, and age-targeted recommendation strategies.
Updated 11 days ago (2026-10-21 08:44 UTC)
MIT
Groundwork
Knowledge & Memory AI & Machine Learning Documentation Access
Rarefied-Earth
F
license
A
quality
D
maintenance
Hosted company-state MCP: brand, voice, charter, priorities, and entitled skills for Cursor, Claude, Codex, OpenClaw, and other MCP hosts. Public proof in under 10 seconds, tenant feed after trial.
Updated 3 months ago (2026-08-14 08:25 UTC)
5
1
-
SandBase MCP bridge
AI & Machine Learning Agent Orchestration Search
Michelle4206
A
license
Not graded
quality
A
maintenance
Enables 25 AI clients to discover, inspect, and run 2,000+ models and APIs through the Model Context Protocol, with free data APIs, OAuth sign-in, and rollback.
Updated 12 days ago (2026-10-20 09:09 UTC)
556,724 npm
MIT

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.

Server Details

Available Tools

Tool Schema Changelog

Related MCP Connectors

Related MCP Servers

Glama MCP Gateway

Resources