Skip to main content
Glama
Sign In
waveform-MCP

waveform-MCP

by jarmstrong158
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

theory_rhythm

Retrieve rhythm and meter details including time signatures, syncopation patterns, and swing ratios. Optionally specify a time signature or syncopation pattern for targeted information, or omit both to access the complete reference.

Instructions

Return rhythm/meter info: time signatures, syncopation patterns, swing ratios. Pass time_sig for one specific time signature, syncopation for one pattern, or neither for the full reference.

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

Input Schema

NameRequiredDescriptionDefault
time_sigNo
syncopationNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations, the description carries the behavioral burden. It clearly states what the tool returns and how parameter choices affect output, but does not mention edge cases (e.g., both parameters provided) or error handling, which would improve transparency.

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 a single, well-structured sentence that front-loads the core purpose and then explains parameter usage. It is concise and easy to parse without unnecessary words.

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

Completeness2/5

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

The description does not specify the output format beyond naming the types of info, and it lacks parameter value formats. For a tool with no output schema and minimal parameter metadata, this is insufficient for reliable invocation; more detail is needed on valid inputs and return structure.

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?

The schema provides only strings with no descriptions. The description says 'time_sig' is 'one specific time signature' and 'syncopation' is 'one pattern', but gives no format examples (e.g., '4/4', pattern names) or allowed values, leaving the agent to guess valid inputs.

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 returns rhythm/meter info (time signatures, syncopation patterns, swing ratios) and specifies how to customize it (pass time_sig, syncopation, or neither). This fully conveys the tool's purpose and scope.

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

Usage Guidelines4/5

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

The description explains when to use each parameter (time_sig, syncopation, or neither), giving the agent actionable guidance. It does not explicitly contrast with sibling theory tools, but the purpose is distinctive enough that this is a minor gap.

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