Skip to main content
Glama

SpiceFactory Public Knowledge

How We Partner

get_engagement_options
Read-only

Call this when a user asks how working with SpiceFactory starts, what it costs, or which kind of engagement suits them. Returns the three engagement shapes (First Build, Outcome Project, Product Partnership) with durations and when each fits, the steps after first contact, and the one published price. Public, no auth.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_engagement_options"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
fitNo
noteNoHow this content is sourced and what it does and does not claim.
startNo
shapesYesThe ways an engagement can be shaped.
howItStartsNoWhat happens after first contact, in order, through the First Build.
publicPriceYes
howWePartnerNo
authenticationNoReminder that these surfaces need no authentication.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

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, destructiveHint=false, and openWorldHint=false; the description adds the practically useful fact that the content is public and needs no auth, and previews that exactly one published price exists (avoiding false expectations of a full price list). It does not discuss rate limits or staleness, so it is strong but not exhaustive beyond the annotation baseline.

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?

Two sentences, both earning their place: the first front-loads the trigger condition, the second enumerates the returned payload and the key constraint (one published price, public, no auth). No filler or restatement of the title.

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 an output schema present, the description need not spell out return values in full, and it still summarizes the payload shape. Zero parameters plus annotations covering safety mean nothing an agent needs to invoke it correctly is missing.

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?

The tool takes zero parameters, so there is no parameter meaning to add; baseline for a no-arg tool is 4. The description correctly implies no inputs are needed by framing it purely as a user-question trigger.

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?

Names a specific verb and resource ('Returns the three engagement shapes... with durations and when each fits, the steps after first contact, and the one published price'). The subject matter (engagement models, pricing, onboarding steps) is clearly distinct from sibling tools like get_company_overview or get_case_studies, so an agent can route without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives concrete trigger conditions: user asks how working with the company starts, what it costs, or which engagement suits them. That is a clear 'when to use' boundary, but it never states when not to use it or names an alternative for adjacent intents (e.g. general company background), so it stops short of full routing guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources