Skip to main content
Glama

watch_folder

Automatically convert new .mscz files in a monitored folder to specified output formats like PDF or MusicXML, with a configurable monitoring duration.

Instructions

Watch a folder for new .mscz files and auto-convert them.

Monitors the folder for up to duration_seconds, converting any new .mscz files that appear into the requested output formats.

Args: folder_path: Absolute path to the folder to watch. output_formats: List of output formats, e.g. ["pdf", "musicxml"]. output_folder: Where to write converted files. Defaults to folder_path. duration_seconds: How long to watch (max 300s).

Returns: {"converted": [{"source": str, "outputs": [str, ...]}, ...], "errors": [{"source": str, "error": str}, ...]}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
folder_pathYes
output_formatsYes
output_folderNo
duration_secondsNo
Behavior3/5

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

No annotations are provided, so the description must fully disclose behavior. It explains the monitoring duration (max 300s) and the return structure. However, it does not clarify whether existing files are ignored, if the tool is read-only or destructive, or if it blocks the process. This leaves some ambiguity.

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

Conciseness5/5

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

The description is well-structured: a brief summary sentence, then a short paragraph, followed by Args and Returns. It is front-loaded with the purpose and every sentence contributes useful information without redundancy.

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?

Given 4 parameters and no output schema, the description covers inputs and outputs thoroughly, including a detailed JSON return structure. It addresses error handling via an 'errors' list. No critical gaps are present.

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

Parameters5/5

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

Schema description coverage is 0%, but the description includes a full Args section with explanations for all four parameters, adding meaning beyond the schema's titles and types. It clarifies default values and expected formats (e.g., 'list of output formats, e.g. ["pdf", "musicxml"]').

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's purpose: watch a folder for new .mscz files and auto-convert them. This is a specific verb ('watch', 'auto-convert') and resource ('folder for .mscz files'), and it distinguishes from siblings like batch_convert or convert_score by introducing the monitoring aspect.

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?

The description does not explicitly state when to use this tool vs alternatives like batch_convert or convert_score. It implies usage for monitoring new files over a duration, but lacks guidance on when not to use it or what distinguishes it from similar tools.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/strongbeen04/MUSESCORE-MCP'

If you have feedback or need assistance with the MCP directory API, please join our Discord server