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

TableJSON Schema
NameRequiredDescriptionDefault
seatsNoStarter 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.
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, starter, leadership-pilot, pilot-meetup, signature-meetup, launch-audit, community-launch, launch-run, hiring, education, vital, visibility, story, product.

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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."
  2. 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"
-]
  3. 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"
+]
  4. 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."
  5. 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"
+}
  6. 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"
+]
  7. 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"
+]
  8. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds valuable behavioral context: the recomputed total is authoritative ('never trust your own arithmetic'), the tool returns selected items with prices and what else the tier could add, and foundation items anchor the package. It also discloses that the context parameter never changes the answer. This goes beyond the annotations without contradicting them.

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

Conciseness5/5

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

The description is compact and front-loaded: the core behavior is in the first sentence, the authoritative-total warning is prominent, and the next-step pointer is at the end. Every sentence earns its place, and the schema parameter descriptions carry the detailed per-parameter guidance. No redundancy with annotations or schema.

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?

For a read-only, idempotent tool with 100% schema coverage and no output schema, the description is nearly complete. It explains the return values (recomputed total, selected items with prices, what else the tier could add), the workflow (call again after every change), and the next step. The only minor gap is that it doesn't explicitly describe error cases or what happens if an invalid preset_id is passed, but the preset_id schema lists valid values. Overall, an agent has enough to call it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the baseline is 3. The description adds meaning beyond the schema: it explains that item_ids come from match_package default_item_ids, that seats is Starter-only and priced per seat with volume bands, and that the bundle price is only the 3-seat entry. The context parameter's purpose is also clarified ('recorded as intent... never changes the answer'). This is meaningful added value over the schema.

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 clear verb-resource pair ('toggle line items, recompute the total') and names the tool as a 'conversational toggle board'. It distinguishes itself from siblings by stating it returns the authoritative recomputed total and by referencing match_package's default_item_ids and request_offer as the next step.

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?

The description explicitly says to call again after every change the visitor asks for, and names the next tool (request_offer). It also tells the agent to advise keeping foundation items. The seats parameter description adds a strong when-to-use rule: ALWAYS ask for headcount before quoting Starter. This is explicit usage guidance beyond the schema.

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