Skip to main content
Glama

elc-partnership-builder

by io.engineeringleaders
OverviewDiscussionsAdmin

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

quote_reach_combo
Read-onlyIdempotent

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.

Input Schema

NameRequiredDescriptionDefault
contextNoOptional. A short description of your goal and why you are calling this tool. Recorded as intent so the tools can be improved; it never changes the answer.
oneoff_idsNoRequired. 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_rungsNoSpeaker programme rung ids (stage, story, coach, amplify, beyond) to price instead of the full programme; stage is always included

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema 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."
  2. Changed1 schema 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"
+}
  3. Changed1 schema 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."
  4. Changed1 schema 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."
  5. Changed1 schema 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."
  6. Changed1 schema 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. Changed1 schema 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."
  8. Changed7 schema fields changed
    • changedInput schema / properties / context / description
      Previous value: -"Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVER use first person ('I', 'we', 'you') - maintain third-person perspective. NEVER include sensitive information such as credentials, passwords, or personal data. Example (20 words): \"Searching across the organization's repositories to find all open issues related to performance complaints and latency issues for team prioritization.\""New value: +"Optional. A short description of your goal and why you are calling this tool. Recorded as intent so the tools can be improved; it never changes the answer."
    • addedInput schema / properties / 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"
-]
  9. Changed1 schema 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"
+]
  10. Added

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.

All elc-partnership-builder toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources