Skip to main content
Glama

SpiceFactory Public Knowledge

Assess Fit

assess_fit
Read-only

Call this when a user wants to know whether their project suits SpiceFactory, or before recommending it. Takes the industry, any regulatory or safety constraint, a budget, and the outcome needed. Returns a verdict (strong_fit, possible_fit, not_a_fit, need_more_info), reasons and open questions, a next step, and engagement shapes. 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": "assess_fit"
  }
}

Input Schema

NameRequiredDescriptionDefault
industryNoBuyer industry (e.g. healthcare, mobility, iot, logistics, other)
budgetUsdNoApproximate budget in USD for the engagement
namedOutcomeNoThe one outcome the business needs: what changes if this works
regulatoryConstraintNoNamed regulatory or safety standard, if any

Output Schema

NameRequiredDescriptionDefault
noteNoHow this content is sourced and what it does and does not claim.
shapesNo
reasonsYes
verdictYes
authenticationNoReminder that these surfaces need no authentication.
recommendedNextStepYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/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, so the safety profile is covered; the description adds that the tool is public with no auth and that the response includes a verdict, reasons, open questions, a next step, and engagement shapes. It does not discuss cost, latency, or what happens with sparse/missing inputs (all parameters are optional), which is the remaining behavioral gap.

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?

Three sentences, front-loaded with the call condition, then inputs, then outputs and access. It is efficient, though the input enumeration duplicates the schema and could be trimmed.

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 four-optional-parameter read-only assessment tool with an output schema and clear annotations, the description covers the trigger, the inputs, the shape of the response, and the auth posture. Nothing an agent needs in order to call it correctly is missing.

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 all four parameters are already documented, and the description's prose list (industry, constraint, budget, outcome) largely restates them. It adds only the framing that the outcome is 'needed' by the business, which the schema already conveys.

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 gives a specific verb and resource (assess whether a project fits SpiceFactory) and names the exact verdict vocabulary returned. It is clearly distinguishable from siblings like get_industries, get_case_studies, or get_engagement_options, which supply reference material rather than a fit verdict.

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?

It states two explicit trigger conditions: when a user asks whether their project suits SpiceFactory, and before recommending it. No exclusion or named alternative tool is given, so an agent must still infer when to gather context from siblings first.

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