Skip to main content
Glama

elc-partnership-builder

by io.engineeringleaders

Report a missing capability — also answers a bare hello/liveness ping

get_more_tools
Read-onlyIdempotent

Check for additional tools whenever your task might benefit from specialized capabilities, even if existing tools could work as a fallback. Also the right tool for a bare greeting (hi, hello), a connectivity/liveness test, or any message too general to match a specific tool below — pass it as context and this returns the full menu instead of a dead end.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
contextYesA description of your goal and what kind of tool would help accomplish it, OR a plain greeting/liveness ping like 'hi' or 'test'.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed2 schema fields changed
    • addedInput schema / $schema
      Added value: +"http://json-schema.org/draft-07/schema#"
    • changedInput schema / properties / context / description
      Previous value: -"A description of your goal and what kind of tool would help accomplish it."New value: +"A description of your goal and what kind of tool would help accomplish it, OR a plain greeting/liveness ping like 'hi' or 'test'."
  2. Added

TDQS

A4.5/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, covering safety. The description adds behavioral context beyond annotations: it returns the full menu instead of a dead end, and it can act as a connectivity/liveness test. This adds useful information about what the tool actually does.

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 concise and front-loaded with the primary purpose, then elaborates on the fallback use case. Every sentence earns its place, and it avoids unnecessary fluff.

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?

Given the tool's simplicity (single parameter, no output schema) and annotations covering safety, the description is complete. It explains when to use it, what to pass, and what the response will be (the full menu). No missing information an agent needs to call it correctly.

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 fully documents the 'context' parameter. The description repeats the same information about greetings and liveness pings, adding no new meaning beyond what the schema provides. Baseline 3 is appropriate.

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 clearly states the tool's purpose: to check for additional tools when a task might benefit from specialized capabilities, and to handle bare greetings or liveness pings as a fallback. It distinguishes itself from siblings by being the catch-all for messages too general to match a specific tool.

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 states when to use it: whenever a task might benefit from specialized capabilities, even if existing tools could work, and for bare greetings or liveness tests. It also implies when not to use it by saying 'too general to match a specific tool', guiding the agent to use specific tools when they apply.

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
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.6/5.0
Disambiguation5/5

Every tool targets a distinct stage or action in the partnership workflow, from discovery (get_partnership_options, get_reach_options) to closing (request_offer, book_intro_call). The only slight overlap between get_started and get_more_tools is clarified by their descriptions—one lists the menu, the other returns the full tool set—so agents can reliably distinguish them. No two tools appear to perform the same function.

Naming Consistency5/5

All tool names follow a consistent verb_noun snake_case pattern (e.g., build_business_case, customize_package, quote_reach_combo). The verbs are action-oriented and the nouns clearly describe the target object or outcome, making the pattern highly predictable across the set.

Tool Count5/5

With 12 tools, the server is well-scoped for a partnership builder covering membership and one-off reach options. Each tool serves a distinct purpose in the sales and customization lifecycle, and the count is within the ideal range where every tool earns its place.

Completeness5/5

The tool surface covers the entire partnership journey: initial qualification, package matching, customization, budget fitting, journey planning, business case generation, quoting, and closing (both offer request and booking). There are no obvious dead ends—even fallback entry points (get_started, get_more_tools) prevent stalled conversations.

Resources