Skip to main content
Glama

arrangement_overview

Map song structure per track as # (clip plays) and . (silent) characters per block of bars to reveal entries, exits, and phrasing at a glance.

Instructions

A map of the Arrangement: for every track, one character per block of block_bars bars ('#' = a clip plays, '.' = silent), so the structure, the entries and exits of each element and the phrasing are visible at a glance.

Parameters:

  • block_bars: Bars per character (default 8)

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

Input Schema

NameRequiredDescriptionDefault
block_barsNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.1.1

TDQS

B3.2/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full load. It does disclose the key behavioral trait — output is a lossy, coarse-grained rendering whose granularity is controlled by block_bars — and the legend makes the result self-interpreting. It does not state that the operation is read-only or how long/large arrangements are handled, leaving some behavioral gaps for a tool with zero annotation coverage.

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 purpose statement is front-loaded and compact, and the character legend does real work. The trailing 'Parameters' block partly restates the schema default of 8, which is slight redundancy, but nothing is bloated.

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?

With an output schema present, the description needn't explain return values, yet it usefully explains the character semantics of the map. For a one-parameter, low-complexity read tool this is close to complete; the only real omission is routing guidance against sibling arrangement-inspection tools.

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

Parameters3/5

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

Schema description coverage is 0%, and the description is the only place 'block_bars' is defined as 'bars per character', which is genuine added meaning beyond the bare integer with a default of 8. However it gives no guidance on picking a value (e.g., smaller for detail, larger for long arrangements) or what happens at extremes.

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 names the resource (the Arrangement) and a specific output form: a per-track character map where '#' means a clip plays and '.' means silence. That is much more concrete than a generic 'get overview' and lets an agent tell it apart from clip-listing siblings, though it never names those siblings explicitly.

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?

Usage is only implied by phrases like 'visible at a glance'; there is no statement of when to reach for this versus get_arrangement_clips or arrangement_templates, and no conditions or prerequisites. An agent must guess that this is the coarse/structural view and the clip tool is the detailed one.

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