Skip to main content
Glama

SpiceFactory Public Knowledge

Primary URLs

get_primary_urls
Read-only

Call this when a user needs a link to a SpiceFactory page, or a machine-readable source to read next. Returns canonical URLs keyed by what they are: how we partner, case studies, industries, contact, and the machine-readable versions (llms.txt, the Markdown homepage, agent skills, the MCP server card). 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_primary_urls"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
homeYes
contactNo
caseStudiesNo
mcpEndpointYes
howWePartnerNo
strategyCallYes
mcpServerCardNo
authenticationNoReminder that these surfaces need no authentication.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint=true, destructiveHint=false, openWorldHint=false), and the description adds what they do not: no authentication is required and the resource is public. It also discloses the return shape as canonical URLs keyed by semantic category, which is behavioral context beyond the annotation set.

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: the first is front-loaded with the invocation condition, the second with the return contract. The enumeration of keys is information-dense rather than padding, and no sentence restates the title or annotations.

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 lookup with an output schema and full annotations, the description supplies everything still missing: when to call it, that it is public and unauthenticated, and what categories of URLs come back. Nothing an agent needs in order to call it correctly is absent.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters and the schema is empty with additionalProperties=false, so there is nothing for the description to disambiguate. The description correctly spends no text on parameter behavior.

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 states a concrete output (canonical URLs keyed by category) and enumerates the key set: partnering, case studies, industries, contact, plus machine-readable artifacts. An agent can tell this is a URL index, not a content retriever, though it never explicitly contrasts itself with siblings like get_case_studies or get_industries, which return the same topics as content.

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 when a user needs a link to a SpiceFactory page, or a machine-readable source to read next" gives a clear trigger condition and implicitly routes machine-readable reading to a follow-up fetch. No explicit exclusions or named alternatives are given, so an agent must infer that get_case_studies is for the case-study content itself rather than the link.

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