Skip to main content
Glama
Sign In
playcal

playcal

by RizgarOzan
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

playcal_audio

Check audio import settings against folder policy and verify WAV loudness, true peak, and clipping offline.

Instructions

check audio import settings (.meta / .import) against a folder policy, and WAV loudness (LUFS), true peak and clipping, offline

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": {
      "action": "<action>"
    },
    "name": "playcal_audio"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathsNoclips to check (default: every audio file in the project)
actionYescheck: import settings against the policy, WAV loudness and peaks
policyNoJSON {"rules": [{"match": "*/UI/*", "load_type": [...], "mono": true, "max_true_peak": -1, "lufs": [lo, hi]}]}; default: UI and SFX in memory, Music streamed, peaks under -1 dBTP
project_pathNoUnity or Godot project folder (default .).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.1

TDQS

B3.3/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It usefully discloses that the operation is 'offline' and framed as a read-style 'check', which tells the agent nothing is mutated in the project. It does not state whether violations cause an error, whether a report is written, or how results are surfaced.

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 front-loaded sentence with the verb first and scoped detail trailing behind parentheses. Dense but every clause carries information; nothing is padding, though the nested parentheses make it slightly harder to scan.

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 four fully documented parameters, no annotations, and no output schema, the description covers the domain and the offline nature of the check. The remaining gap is what a 'check' returns or does on a policy violation, which the agent must infer, but that is a modest omission.

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?

Schema coverage is 100%, so the baseline is 3, but the description adds essentially nothing beyond the schema: 'folder policy' is already the documented concept for the policy parameter, and the .meta/.import mention maps to nothing param-specific. It clarifies the domain, not the meaning of any individual parameter, so it sits just under the baseline.

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?

Names a specific verb ('check') and two concrete resources: audio import settings (.meta/.import) against a folder policy, and WAV loudness/true peak/clipping. An agent knows exactly what domain this covers. It does not, however, differentiate itself from siblings like playcal_meta (which plausibly also touches .meta files) or playcal_loop.

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?

Usage is implied rather than stated: 'offline' signals this can run without an open editor, and the pairing of policy-checking with loudness metering implies a validation/QA use case. But there is no explicit when-to-use vs. when-not, and no alternative sibling (e.g. playcal_meta for non-policy metadata checks, playcal_loop for loop-point validation) is named.

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