Skip to main content
Glama

elc-partnership-builder

by io.engineeringleaders
OverviewDiscussionsAdmin

Customize a package: toggle line items, recompute the total

customize_package
Read-onlyIdempotent

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.

Input Schema

NameRequiredDescriptionDefault
seatsNoSeat-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).
contextNoOptional. A short description of your goal and why you are calling this tool. Recorded as intent so the tools can be improved; it never changes the answer.
item_idsNoRequired. Item ids currently toggled ON (from match_package default_item_ids, plus/minus changes)
preset_idNoRequired. 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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema 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)."
  2. Changed1 schema 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."
  3. Changed1 schema 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."
  4. Changed1 schema 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."
  5. Changed10 schema fields changed
    • changedInput schema / properties / context / description
      Previous value: -"Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVER use first person ('I', 'we', 'you') - maintain third-person perspective. NEVER include sensitive information such as credentials, passwords, or personal data. Example (20 words): \"Searching across the organization's repositories to find all open issues related to performance complaints and latency issues for team prioritization.\""New value: +"Optional. A short description of your goal and why you are calling this tool. Recorded as intent so the tools can be improved; it never changes the answer."
    • addedInput schema / properties / item_ids / anyOf
      Added value: +[
+  {
+    "items": {
+      "type": "string"
+    },
+    "type": "array"
+  },
+  {
+    "type": "string"
+  }
+]
    • 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"
-]
  6. Changed2 schema fields changed
    • addedInput schema / properties / context
      Added value: +{
+  "description": "Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVER use first person ('I', 'we', 'you') - maintain third-person perspective. NEVER include sensitive information such as credentials, passwords, or personal data. Example (20 words): \"Searching across the organization's repositories to find all open issues related to performance complaints and latency issues for team prioritization.\"",
+  "type": "string"
+}
    • changedInput schema / required
      Previous value: -[
-  "preset_id",
-  "item_ids"
-]New value: +[
+  "preset_id",
+  "item_ids",
+  "context"
+]
  7. Changed2 schema 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."
  8. Changed1 schema 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"
+}
  9. Changed1 schema field changed
    • changedInput schema / properties / preset_id / enum
      Previous value: -[
-  "free",
-  "leadership-pilot",
-  "pilot-meetup",
-  "vital",
-  "hiring",
-  "visibility",
-  "education",
-  "product",
-  "story"
-]New value: +[
+  "free",
+  "leadership-pilot",
+  "pilot-meetup",
+  "team",
+  "vital",
+  "hiring",
+  "visibility",
+  "education",
+  "product",
+  "story"
+]
  10. Changed1 schema field changed
    • changedInput schema / properties / preset_id / enum
      Previous value: -[
-  "free",
-  "leadership-pilot",
-  "pilot-meetup",
-  "orbit",
-  "nebula",
-  "supernova",
-  "quasar"
-]New value: +[
+  "free",
+  "leadership-pilot",
+  "pilot-meetup",
+  "vital",
+  "hiring",
+  "visibility",
+  "education",
+  "product",
+  "story"
+]
  11. First observed

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.

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