Skip to main content
Glama

elc-partnership-builder

by io.engineeringleaders
OverviewDiscussionsAdmin

Compute the ROI case and a forwardable approval memo

build_business_case
Read-onlyIdempotent

Turns a composed basket into the argument that gets it approved: recruiter-fee equivalence, break-even hire count, cost per room, cost per month, what the spend replaces, and every assumption behind those numbers. Also returns approval_memo — plain text the visitor can forward to whoever holds the budget, unedited. Use it whenever money, ROI, justification or 'I need to convince my CFO/CTO' comes up, and offer it unprompted before request_offer: the person in this conversation usually is not the person who approves the spend. Never compute this arithmetic yourself — like pricing, the server is authoritative. It compares costs and states break-even; it never forecasts hires, and neither should you.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
kpisNoOptional: what has to move this year, in their words
companyNoOptional: company name, for the memo
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. The basket: item ids toggled ON
preset_idNoRequired. The package being justified One of: free, starter, leadership-pilot, pilot-meetup, signature-meetup, launch-audit, community-launch, launch-run, hiring, education, vital, visibility, story, product.
requester_nameNoOptional: who is asking for approval, signed at the memo's foot
open_senior_rolesNoOptional: senior roles they need to fill in 12 months — sharpens the comparison into their numbers
avg_first_year_salaryNoOptional: average first-year salary in EUR for those roles; turns the generic fee band into their own

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 justified One of: free, starter, leadership-pilot, pilot-meetup, hiring, education, vital, visibility, story, product."New value: +"Required. The package being justified One of: free, starter, leadership-pilot, pilot-meetup, signature-meetup, launch-audit, community-launch, launch-run, hiring, education, vital, visibility, story, product."
  2. Changed12 schema fields changed
    • addedInput schema / properties / avg_first_year_salary / anyOf
      Added value: +[
+  {
+    "type": "number"
+  },
+  {
+    "type": "string"
+  }
+]
    • removedInput schema / properties / avg_first_year_salary / 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 / item_ids / anyOf
      Added value: +[
+  {
+    "items": {
+      "type": "string"
+    },
+    "type": "array"
+  },
+  {
+    "type": "string"
+  }
+]
    • changedInput schema / properties / item_ids / description
      Previous value: -"The basket: item ids toggled ON"New value: +"Required. The basket: item ids toggled ON"
    • removedInput schema / properties / item_ids / items
      Removed value: -{
-  "type": "string"
-}
    • removedInput schema / properties / item_ids / type
      Removed value: -"array"
    • addedInput schema / properties / open_senior_roles / anyOf
      Added value: +[
+  {
+    "type": "number"
+  },
+  {
+    "type": "string"
+  }
+]
    • removedInput schema / properties / open_senior_roles / type
      Removed value: -"number"
    • changedInput schema / properties / preset_id / description
      Previous value: -"The package being justified"New value: +"Required. The package being justified 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",
-  "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. 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"
+]
  5. Added

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already declare this as read-only, idempotent, and non-destructive, but the description adds valuable context beyond those hints: the server is authoritative over arithmetic, the tool never forecasts hires (and the agent shouldn't either), and it returns an unedited approval_memo. These details help set appropriate expectations.

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 front-loaded with the core purpose and output metrics, then covers usage triggers and critical constraints in a logical sequence. Every sentence delivers functional value: purpose, outputs, usage condition, and a critical warning about not computing arithmetic manually. It is dense but not bloated.

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?

With no output schema, the description thoroughly explains the return values (all listed metrics and the approval_memo) and the tool's limitations (no forecast hires). It also covers usage conditions and the authoritative nature of the server, making the tool well-specified even with 8 parameters.

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 coverage is 100%, so the baseline for parameter semantics is 3. The description does not add parameter-specific detail beyond what the schema already provides; it focuses on outputs and usage. The only indirect reference is 'composed basket,' which vaguely implies item_ids and preset_id but lacks parameter-level specificity.

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 states a specific action ('Turns a composed basket into the argument that gets it approved') and enumerates concrete outputs (recruiter-fee equivalence, break-even hire count, cost per room, etc.). It also distinguishes itself from siblings by explicitly positioning it before request_offer, making its role 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?

The description gives explicit when-to-use guidance ('Use it whenever money, ROI, justification or I need to convince my CFO/CTO comes up') and recommends offering it unprompted before request_offer. It also provides a clear boundary ('Never compute this arithmetic yourself') and a behavioral constraint ('it never forecasts hires, and neither should you'), leaving no ambiguity about invocation.

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