Skip to main content
Glama

List Kits

list_kits
Read-onlyIdempotent

List the 12 themed kits with pricing and member products. FREE.

Takes no arguments. Returns a list of kit objects, each {"slug": ..., "name": ..., "price_usd": N, "tagline": ..., "members": ["product-slug", ...], "availability": ...}. Use a kit's slug with get_full_kit (premium). Kits are not sold standalone on any marketplace: price_usd is the bundle's reference value, and All-Access is how a caller actually unlocks one.

Use when the caller asks about bundles or bundle pricing. Not for individual products (search_catalog) and not for a kit's full contents (get_full_kit). Errors: on invalid, missing, or malformed input this tool never raises a protocol error; it returns {"error": ""}. Every call is read-only and idempotent, so after correcting the input it is always safe to retry.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered; the description still adds genuinely new behavior: it never raises a protocol error, it returns an {"error": ...} object instead, and retry after correction is safe. It also discloses non-obvious business semantics (kits are not sold standalone; price_usd is a reference value and All-Access is the real unlock), which no structured field conveys.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with purpose, then return shape, then routing guidance, then error contract - good ordering. The inline enumeration of every return field duplicates the output schema and could be shortened to a pointer, but the rest earns its space.

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-argument read tool with an output schema and full annotations, nothing an agent needs is missing: trigger, exclusions, return shape, error behavior, and the business caveat about pricing and All-Access unlocking are all present.

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?

Zero parameters, so there is no parameter semantics to explain and the schema is fully empty by design. The description correctly notes 'takes no arguments', matching the schema with no claims to verify.

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?

States a specific verb and resource ('List the 12 themed kits with pricing and member products') and immediately scopes it as argument-free and FREE. It explicitly distinguishes itself from search_catalog and get_full_kit, so an agent can route without opening a schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives both the positive trigger ('when the caller asks about bundles or bundle pricing') and explicit exclusions pointing at the correct siblings for the two adjacent cases (individual products -> search_catalog, full contents -> get_full_kit). Nothing is left to inference.

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.