Skip to main content
Glama

elc-partnership-builder

by io.engineeringleaders
OverviewDiscussionsAdmin

Compose the best package for an exact budget

fit_to_budget
Read-onlyIdempotent

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.

Input Schema

NameRequiredDescriptionDefault
budgetNoRequired. The visitor's ceiling in EUR, as a number (8000, not '8K')
againstNoPrice the budget against the list price. 'discounted' equals list since the AI channel carries no discount (2026-10-05) One of: discounted, list.
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.
must_haveNoOptional: item ids the visitor explicitly asked for; kept first if they fit
preset_idNoRequired. 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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema 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."
  2. Changed1 schema 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."
  3. Changed1 schema 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."
  4. Changed1 schema 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."
  5. Changed1 schema 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."
  6. Changed12 schema 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"
-]
  7. 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",
-  "budget"
-]New value: +[
+  "preset_id",
+  "budget",
+  "context"
+]
  8. Changed1 schema 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"
+]
  9. Added

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.

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