Skip to main content
Glama

list_pack

Lists .mid files in a generated pack folder along with their file sizes to verify exported MIDI stems before loading them into a DAW.

Instructions

List the .mid files in a generated pack folder with sizes.

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": {
      "out_dir": "<out_dir>"
    },
    "name": "list_pack"
  }
}

Input Schema

NameRequiredDescriptionDefault
out_dirYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3/5.0
Behavior3/5

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

With no annotations, the description bears the full burden; it does at least clarify this is a read-style listing and states that results include file sizes, which substitutes for the missing output schema. It says nothing about behavior when the folder is missing, whether listing is recursive, or whether hidden files are excluded. Meaningful but incomplete behavioral context for a no-annotation tool.

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?

A single compact sentence with the resource and return content front-loaded and no filler. It is efficient, though its brevity contributes to the gaps in usage and parameter guidance rather than being a virtue in itself.

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

Completeness3/5

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

For a simple one-parameter listing tool with no output schema and no annotations, the description covers the essentials of what it returns. It falls short on the ambiguity most likely to bite an agent: what out_dir should look like, and what happens if the folder does not exist.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

There is one required parameter, out_dir, with 0% schema description coverage, so the description must carry the meaning. Referring to a 'pack folder' loosely gestures at a directory, but gives no guidance on path format, relative versus absolute paths, or whether the directory must exist. The only parameter an agent must supply remains semantically underspecified.

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?

The description gives a specific verb and resource: list .mid files in a generated pack folder, plus the returned attribute (sizes). That is far more concrete than a tautology. It does not, however, distinguish itself from siblings like analyze_song or generate_arrangement, though those appear functionally distinct.

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

Usage Guidelines2/5

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

There is no explicit guidance on when to call this versus alternatives, nor any stated precondition such as the pack having already been generated. The phrase 'generated pack folder' only weakly implies post-generation usage. An agent must infer the trigger condition on its own.

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