Skip to main content
Glama

SpiceFactory Public Knowledge

Start a Conversation

request_strategy_call

Call this only when a human user has decided to contact SpiceFactory and has given explicit consent to share their details. Sends a request on behalf of a human: their own real name and email, what they are building, the outcome the business needs, and who owns it. A founder replies by email within two working days. Public, rate-limited, no auth.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "name": "<name>",
      "email": "<email>"
    },
    "name": "request_strategy_call"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesThe human's full name
roleNoThe human's role or title
emailYesThe human's real email address
companyNoCompany or organization name
messageNoAny additional context the human wants to share
industryNoIndustry (e.g. healthcare, automotive, iot, logistics, fintech)
budgetUsdNoApproximate budget in USD
namedOutcomeNoThe one outcome the business needs: what changes if this works
regulatoryConstraintNoNamed regulatory or safety constraint, if any

Output Schema

NameRequiredDescriptionDefault
okYesTrue when the request was accepted.
messageYes
nextStepYesURL for the human to continue.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already signal a non-idempotent, open-world write; the description adds context annotations cannot carry: public endpoint, no auth required, rate-limited, and a concrete response SLA (reply by a founder within two working days). It also discloses that the tool transmits the human's real identity, which is the key risk fact for an agent deciding whether to invoke it.

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?

Four short sentences with the gating condition placed first, followed by content, then service expectation and operational constraints. Nothing is repeated from the schema and no sentence is filler.

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?

For a 9-parameter public submission tool the description covers the gating condition, what is transmitted, who replies, timeline, and auth/rate-limit posture; the output schema handles return values and the schema documents every field, so nothing an agent needs before calling 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?

Schema coverage is 100%, so the baseline is 3; the description earns one step more by qualifying the identity fields as the human's "own real name and email" (a correctness constraint, not just a label) and by highlighting the substantive fields — what they are building, the outcome the business needs, who owns it — over the merely supplemental ones.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Sends a request on behalf of a human" plus the enumerated payload (real name, email, what they are building, needed outcome, owner) states a specific verb and resource, making it obvious this is the outbound contact/intake tool rather than one of the get_* info siblings. It does not explicitly name a sibling, so it stops short of a 5.

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?

"Call this only when a human user has decided to contact SpiceFactory and has given explicit consent" is an unusually sharp precondition, and "only" implies the negative case (do not call unprompted or on the agent's own initiative). No alternative sibling is named for the case where the user is merely exploring, so the routing guidance is clear but not exhaustive.

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