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

TableJSON 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, 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 / 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."
  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, 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."
  3. 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"
-]
  4. 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"
+]
  5. 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"
+]
  6. Added

TDQS

A4.8/5.0
Behavior5/5

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

Annotations cover safety (readOnly, idempotent, non-destructive), and the description adds substantial context beyond them: deterministic composition, the ordering algorithm (foundation items first, then cheapest-first), the default pricing channel, and the four things the response contains. This is rich behavioral disclosure.

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 trigger condition is front-loaded and the return contents are enumerated compactly. The final sentence about authority is slightly redundant with the earlier 'never hand-pick' instruction, but the length is justified by the amount of behavioral information conveyed.

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, yet the description enumerates what is returned (what fits, what was excluded and why, unspent budget, cheapest excluded item) and explains the default pricing basis. An agent has everything needed to call and interpret this 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 coverage is 100%, so the baseline is 3. The description goes further by explaining that pricing defaults to the AI-channel figure because that is what the visitor actually pays, which clarifies the meaning/default of the `against` parameter beyond the schema's wording.

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 action (compose the best-value package under a stated budget) and a precise trigger condition (a number rather than a band). It is clearly separable from siblings match_package (choose a preset) and customize_package (total a hand-built basket).

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 ('when the visitor names a NUMBER'), an explicit when-not/do-this-instead ('Never hand-pick a basket yourself when a budget is stated'), and it names the sibling whose authority it parallels. 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