Skip to main content
Glama

SpiceFactory Public Knowledge

Industries

get_industries
Read-only

Call this when a user asks whether SpiceFactory has worked in their industry or under their regulator. Returns healthcare and medtech, mobility, IoT, and logistics, with what was built in each and case-study URLs, plus the compliance work done with partners (HIPAA, SOC 2, PCI DSS, FDA documentation for a client's submission). 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_industries"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/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 the useful operational fact that the data is public and needs no authentication, plus the shape of what comes back; it does not discuss rate limits or caching, but nothing material is missing.

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?

The triggering condition is front-loaded in the first sentence, and the second sentence packs the return contents and auth note without filler. The industry enumeration makes the second sentence dense, but each listed item is differentiating information rather than padding.

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 zero-parameter, read-only lookup this is fully adequate: when to call it, what categories come back, that case-study URLs are included, and that no auth is needed. An output schema exists, so return values need not be specified further, and the description still summarizes them usefully.

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 the baseline is 4 and there is nothing for the description to disambiguate. It correctly implies a parameterless lookup by describing a single fixed catalog of industries rather than a filtered query.

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?

The description gives a concrete verb and resource (returns the industries SpiceFactory has worked in) and enumerates the actual content: healthcare and medtech, mobility, IoT, logistics, case-study URLs, and compliance work. It stops short of explicitly distinguishing itself from the sibling get_case_studies, which likely returns overlapping case-study material, so an agent must infer the split.

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 gives a clear trigger: call this when a user asks whether SpiceFactory has worked in their industry or under their regulator. There are no explicit when-not conditions or named alternatives, but the triggering question is specific enough to route most cases correctly.

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