Skip to main content
Glama
romanstark

Live Maestro

by romanstark
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

sound_index_status

Read-onlyIdempotent

Check if the sound library index exists and inspect its details: location, build time, item counts, and skipped items. Confirm the index is ready before matching sounds to avoid missing rankings.

Instructions

Is there an index of how this installation's library sounds, and what is in it?

Call this before ``match_sound``. Without an index that tool has nothing to rank
against, and a fresh session has no way of knowing whether one was ever built.

Returns:
    Dictionary with whether an index exists, where it is, when it was built, how
    many items of each kind it carries, which libraries they came from, and what
    was skipped when it was built.

Note:
    The index is built from the audio Ableton renders for its own browser previews,
    which sits beside the content under ``Ableton Folder Info/Previews``. It is not
    committed and it describes one machine: rebuild it by running
    ``live-maestro-index`` after installing or removing packs.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already declare readOnlyHint=true, openWorldHint=false, idempotentHint=true, and destructiveHint=false. The description adds meaningful behavioral context: the index is not committed, describes one machine, is built from Ableton preview renders, and lives under a specific path. This is valuable information that annotations do not provide.

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?

The description is well-structured with a clear question, a usage directive, a returns summary, and a note. It is slightly longer than strictly necessary, but every section adds relevant information and the most important guidance ('Call this before match_sound') is front-loaded.

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-parameter read-only status tool with an output schema, the description is complete: it covers what the tool does, when to call it, what it returns, and important environmental caveats. An agent has everything needed to invoke it correctly and interpret its role in the workflow.

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 has zero parameters and the schema is empty, so the baseline is 4. The description does not need to explain parameter semantics since there are none, and it does not introduce any misleading parameter-related claims.

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?

The description clearly states the tool is a status check for a sound index: it asks and answers whether an index exists and what it contains. It names the specific resource (the installation's library sound index) and differentiates itself from its sibling match_sound by establishing a dependency relationship.

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?

The description gives explicit when-to-use guidance: 'Call this before match_sound' and explains why (without an index, match_sound has nothing to rank against). It also tells the agent when the index needs rebuilding via live-maestro-index, which is practical usage context beyond simple selection.

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