list_loadoutsList curated loadouts — deliberately-assembled kits of MCP servers + governance + plays for a specific job (GTM, coding, research, support, infra). The agent-facing version of the /loadouts product. Use get_loadout for the full kit with live trust.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided, so description carries full burden. It describes a read-only list operation with no side effects. Adds context about the nature of loadouts. Does not detail authentication or empty results, but for a simple list tool this is adequate.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two sentences, no unnecessary words. Front-loaded with verb 'List', then explains what loadouts are and directs to alternative. Highly concise.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given no output schema, no parameters, and low complexity, the description is complete. It explains what is listed, the nature of the items, and points to get_loadout for more detail. No gaps.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
No parameters in schema, so no additional meaning needed beyond what descriptor provides. The description adds context about what loadouts are, which indirectly clarifies that no parameters are needed.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool lists curated loadouts and explains what loadouts are (kits of MCP servers, governance, plays for jobs). It also distinguishes from sibling get_loadout by noting that list_loadouts is the agent-facing version and directing to get_loadout for full kit with live trust.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Explicitly tells when to use this tool (for overview of curated loadouts) and when to use alternative get_loadout (for full kit with live trust). Provides context that this is the agent-facing version of the /loadouts product.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool targets a distinct operation: checking trust, comparing servers, generating configs, fetching records, listing capabilities or loadouts, searching, planning, and reporting. No two tools overlap in purpose; even similar verbs like 'get' and 'list' are applied to different resources.
All tools follow a consistent verb_noun pattern in snake_case (e.g., check_trust, get_server, list_capabilities). The verbs are specific and descriptive, and the nouns clearly indicate the target resource or action.
14 tools is well-scoped for a server that indexes and evaluates MCP servers. The number is sufficient to cover core operations (retrieval, comparison, configuration, planning, reporting) without being overwhelming or redundant.
The tool surface covers all essential interactions: exploring servers, capabilities, loadouts, and stats; comparing and trusting; generating configs; planning toolkits; and reporting issues. The domain is fully served with no obvious missing capabilities.