Nopaque TotalPath

Get Audio File

getAudio

Read-onlyIdempotent

Get one audio file's metadata by id: category, filename, content type, size, duration, format, what it belongs to and when it was created. Metadata only, never the audio or a link to it. Use when: a profile or test names an audio id and you want to say what it is. Read-only. Needs audio:read. Returns 404 if the file is not in your workspace.

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": {
      "id": "<id>"
    },
    "name": "getAudio"
  }
}

Input Schema

Name	Required	Description	Default
`id`	Yes	Audio metadata identifier.

Output Schema

Name	Required	Description
`id`	Yes	Audio metadata identifier.
`s3Key`	Yes	S3 object key inside the audio bucket. Treat as opaque and never rebuild it from other fields: new uploads get a key that is unique per upload, while rows created before that change keep their original key.
`format`	No	Lowercase file extension derived from filename. Optional.
`category`	Yes	Bucket used by the upload-URL handler to derive the S3 key. Audio files for test runs live under `tests/`, mapping recordings under `maps/`, voice profiles under `voices/`, and transcript audio under `transcripts/`.
`channels`	No	Channel count (1=mono, 2=stereo), when known.
`filename`	Yes	Original client-supplied filename (sanitised for the S3 key).
`metadata`	No	Arbitrary client-supplied metadata captured at upload time.
`createdAt`	Yes	ISO-8601 timestamp of metadata creation.
`createdBy`	Yes	User id that initiated the upload.
`expiresAt`	No	Optional TTL (epoch seconds). Audio with `expiresAt` will be auto-deleted by DynamoDB TTL — present only on ephemeral/test audio.
`sizeBytes`	Yes	Declared object size in bytes. Rows created before `sizeBytes` became required on upload may hold 0.
`sampleRate`	No	Sample rate in Hz, when known.
`contentType`	Yes	MIME type captured at upload time.
`workspaceId`	Yes	Workspace that owns this audio.
`associatedId`	Yes	Owning entity id — `runId` for `test`/`map` category, `voiceId` for `voice` category. Defaults to the audio id when no parent is supplied at upload time.
`durationSecs`	No	Audio duration in seconds (optional — may be 0 or absent).

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 11, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Beyond the annotations (which already cover read-only and idempotency), the description adds the required scope (audio:read) and the failure mode (404 when the file is not in your workspace), both of which the agent needs to call and interpret results safely. It also preempts a likely misuse by stating the response never includes audio or a link to it.

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?

Four tight sentences, each carrying distinct information: identity, contents, trigger, and constraints. The exclusion and the error behavior are front-loaded rather than buried, and there is no filler.

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?

An output schema exists, yet the description still gives a useful field summary, and it covers the areas the schema cannot: auth scope, workspace-bound 404 behavior, and the metadata-only contract. Nothing an agent needs in order to invoke this correctly is missing.

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?

There is a single parameter with 100% schema description coverage and a declared uuid format, so the schema does the work. The description only echoes "by `id`" without adding format or sourcing guidance, which matches the baseline for a fully documented single-param schema.

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?

States a specific verb and resource ("Get one audio file's metadata by `id`") and enumerates the returned fields, so the agent knows exactly what comes back. It also draws a hard boundary that no sibling tool provides: metadata only, never the audio itself or a link to it.

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 "Use when: a profile or test names an audio id" clause gives a concrete trigger, and the metadata-only caveat tells the agent when this tool will not satisfy an audio-content request. It does not name a sibling alternative such as listAudio for enumerating files, so the routing guidance stops short of explicit when-not/alternatives.

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

All Nopaque TotalPath tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.