Skip to main content
Glama

Search loadouts

search_loadouts
Read-onlyIdempotent

Search SetupBay for rule/skill/MCP bundles. Ranked by relevance to query; filter by agent, tags (stacks such as nextjs, godot, python) or category. With no query, lists loadouts (featured and verified first).

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": "search_loadouts"
  }
}

Input Schema

NameRequiredDescriptionDefault
hasNoOnly loadouts containing skills, MCP configs or rules
tagsNoAll of these stacks/categories must match, e.g. ["typescript"]
agentNoOnly loadouts that support this agent
limitNoMax results (default 10)
queryNoFree text, e.g. 'nextjs supabase auth' or 'discord bot'
categoryNoCategory id (see list_tags)
verified_onlyNoOnly loadouts that passed the Level 1 automated install check

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 declare read-only, idempotent, non-destructive, closed-world behavior, so the description needn't restate safety. It adds genuine context beyond them: ranking is by relevance to `query`, and an empty query yields a featured/verified-first listing order, which affects how an agent should interpret results.

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 dense sentences with the primary action and core filters front-loaded, followed by the no-query fallback. No filler or restated title.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

All seven parameters are optional and fully documented in the schema, and the description covers mode selection, ranking, and filtering, which is what an agent needs to call it. It omits result shape and result-count behavior, but with no output schema that is a minor gap for a search tool whose annotations cover the safety profile.

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?

Schema coverage is 100%, so the baseline is 3; the description still adds meaning by explaining what `query` does when present versus absent and by framing `tags` as stacks (nextjs, godot, python) versus `category` as a separate axis. It does not clarify `limit`, `has`, or `verified_only` beyond the schema.

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?

"Search SetupBay for rule/skill/MCP bundles" names a specific verb and resource, and the following clause names the ranking model and the available filter axes. Combined with the sibling set (get_loadout, list_tags), an agent can tell this is the discovery tool rather than a single-item fetch.

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?

Explicitly covers the two modes: with a `query` it ranks by relevance, with no query it lists loadouts (featured and verified first). It does not name alternatives such as get_loadout for fetching one result or list_tags for resolving a category id (that pointer lives only in the schema).

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.