Skip to main content
Glama
Podcast MCP
by calebn

kit_list_tool

Lists each show kit’s newest version with its count of missing segments, flagging damaged versions and their problem codes so users can check kit status before editing.

Instructions

List the show kits: the newest version of each, with how many of its segments are missing.

A kit whose newest version is damaged is listed as {"id", "version", "damaged": true, "problem", "code"}. Read-only; kits are per user, like the segment library.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.4

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the burden and does add real behavioral context: it declares read-only behavior, states kits are per user, and documents the special 'damaged' return shape. However it says nothing about ordering, volume, or what happens when a user has no kits, so the disclosure is partial rather than rich.

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?

Two tightly written sentences with the core behavior front-loaded and the edge case (damaged newest version) second. The embedded JSON snippet is slightly noisy in prose form and the double-backtick escapes are an artifact, but nothing is redundant.

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?

For a zero-argument, read-only list tool with an output schema already defining return values, the description covers scope, safety, tenancy, and the one anomalous result case. Only the absence of ordering or empty-result behavior keeps it from being fully complete.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate; baseline 4 applies. The description correctly avoids inventing filter arguments that do not exist.

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?

States a specific verb and resource ('List the show kits') plus the scoping rule that only the newest version of each kit is returned. An agent can tell this apart from kit_show_tool or kit_save_tool without opening another schema. It stops short of naming siblings explicitly, so it lands at 4 rather than 5.

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

Usage Guidelines3/5

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

Usage is only implied: the description makes clear this is the enumeration entry point for kits, and 'Read-only' hints it is safe to call freely. There is no statement of when to prefer this over kit_show_tool, nor any exclusion or prerequisite, so the agent must infer the routing.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools