Skip to main content
Glama

SpiceFactory Public Knowledge

Search Essays and Case Studies

search
Read-only

Call this when a user asks what SpiceFactory has written or built on a topic, such as FDA evidence for AI software, HIPAA architecture, or fleet telemetry. Searches recent essays, case studies, and the main pages. Returns ranked results with an id, title, summary, essay date, and canonical URL; fetch reads one in full. Public, 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": {
      "query": "<query>"
    },
    "name": "search"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeNoLimit results to essays (blog), case studies, or pages. Omit to search everything.
limitNoNumber of results, 1 to 10. Default 5.
queryYesA few topic words, e.g. 'predetermined change control plan' or 'surgery center patient tracking'

Output Schema

NameRequiredDescriptionDefault
noteNoHow this content is sourced and what it does and does not claim.
resultsYesBest matches first.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Beyond the annotations (readOnly/destructive false), the description adds real behavioral context: the corpus is public with no auth required, results are ranked rather than unordered, and the covered sources are limited to recent essays, case studies, and main pages. The no-auth note is exactly the kind of operational detail annotations do not convey.

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 front-loads the trigger and examples, the second covers return shape, follow-up routing, and access requirements. No filler or repetition.

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 three-parameter read-only search with an output schema and full schema coverage, the definition covers trigger, scope, result shape, next step, and access conditions. Nothing needed to invoke 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 coverage is 100% and each parameter already carries a description and example, so the schema does the heavy lifting. The description's phrase "a few topic words" loosely reinforces the query style but adds little beyond what the schema states.

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?

"Searches recent essays, case studies, and the main pages" is a specific verb+resource with an explicit corpus scope, and the contrast with "fetch reads one in full" separates search from retrieval. Concrete example topics (FDA evidence for AI software, HIPAA architecture, fleet telemetry) make the resource unmistakable.

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 asks what SpiceFactory has written or built on a topic" gives a clear triggering condition, and it routes follow-up reading to fetch. It stops short of stating exclusions (e.g., when a direct listing tool would be preferable), so it is clear but not fully discriminating.

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