Skip to main content
Glama

aw.audio.trim

Copy the current source-frame interval using the unchanged core floor-to-frame semantics.

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": {
      "session": "<session>",
      "operationId": "<operationId>",
      "source": "<source>",
      "startSeconds": "<startSeconds>",
      "endSeconds": "<endSeconds>"
    },
    "name": "aw.audio.trim"
  }
}

Input Schema

NameRequiredDescriptionDefault
sourceYesAn immutable input or result handle belonging to this session; never a URL/path/base64.
float32No
sessionYesPrivate short-lived session capability returned by aw.session.open. Never publish or log it.
endSecondsYes
operationIdYesStable operation UUID for safe retry/reconciliation; reuse only with identical sources/settings.
startSecondsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false and destructiveHint=false, so the safety profile is covered; the word "Copy" usefully implies the source is left intact, which is consistent with those hints. However, "unchanged core floor-to-frame semantics" is undefined internal jargon that does not explain boundary rounding, whether a new artifact handle is created, or how output is retrieved. No contradiction with annotations.

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

Conciseness3/5

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

It is a single front-loaded sentence with no filler, so it is concise. But brevity here comes at the cost of intelligibility, since the one sentence is dominated by an unexplained phrase ("unchanged core floor-to-frame semantics").

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?

This is a 6-parameter, 5-required mutation-adjacent tool with no output schema, and the description never says what is produced (a new artifact handle?) or how the caller obtains the result. For a tool that creates a copied interval, that is a meaningful gap the schema cannot fill.

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 50%: source, session, and operationId are documented in the schema, while startSeconds, endSeconds, and float32 are not. "Floor-to-frame semantics" gestures at how the second-valued bounds map to frames, which is the one piece of meaning added beyond the schema, but it is too cryptic to be actionable.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Copy the current source-frame interval" restates the trim operation in abstract terms without ever saying it extracts/copies a segment of audio defined by start and end times. The verb "Copy" plus the resource "source-frame interval" is nearly circular with the tool name and does not let an agent distinguish it from a sibling like aw.audio.reverse.

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?

There is no when-to-use guidance, no statement of prerequisites (an open session and an input/artifact source handle), and no mention of how this differs from other audio tools. The agent must infer usage entirely from the name and schema.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources