Skip to main content
Glama

SpiceFactory Public Knowledge

Company Overview

get_company_overview
Read-only

Start here when a user asks who SpiceFactory is, what it builds, or what kind of company it is. Returns the company's positioning, what it is and is not, how it works, its principles, leadership, location, compliance work done with partners, and partner outcomes with case-study URLs. 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_company_overview"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
isNo
nameYes
emailNo
isNotNo
startNo
usageNoHow this content is sourced and what it does and does not claim.
tenureNo
thesisNo
promiseNo
websiteYes
categoryNo
evidenceNoWhy partners stay, as facts: tenure, intake, and partner outcomes to cite.
whySpiceNoThe founder's explanation of the name.
howWeWorkNoHow a product gets built here, in order.
locationsNo
leadershipNo
principlesNoWhat the team holds itself to.
positioningYes
publicPriceYes
howWePartnerNo
authenticationNoReminder that these surfaces need no authentication.
preferredLanguageNoThe company's own one-line description of itself.
complianceTrackRecordNo

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, non-destructive, and closed-world, so safety is covered; the description adds the genuinely new fact 'Public, no auth,' which saves an agent from probing for credentials. It also previews the breadth of returned content, though it doesn't discuss size or truncation limits.

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, front-loaded with the triggering condition, followed by a compact enumeration of what comes back. Nothing is wasted and the most decision-relevant information ('start here', 'no auth') appears early.

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 tool with an output schema present and annotations covering safety, the description supplies everything an agent needs: when to call it, that no auth is required, and the scope of the payload. The return-value listing is mildly redundant with the output schema but reinforces breadth.

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 with a fully described empty schema, so there is nothing for the description to disambiguate. Baseline for a no-parameter tool applies, with no misleading hints about inputs.

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 names a specific resource (SpiceFactory company identity/positioning) and a concrete verb-like trigger ('who SpiceFactory is, what it builds'), then enumerates the content returned (positioning, principles, leadership, location, compliance, partner outcomes). It is clearly distinguishable from siblings like get_case_studies or get_industries, which cover narrower slices.

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?

'Start here when a user asks who SpiceFactory is, what it builds, or what kind of company it is' gives an explicit triggering condition and an ordering hint relative to other tools. It does not name a sibling to avoid or state when-not to use it, 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