Skip to main content
Glama
Sign In
Tapra MCP server

Tapra MCP server

Official
by tapra-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Play audio

play_audio
Read-onlyIdempotent

Play an audio or video file on the computer's speakers, returning immediately while playing; a new play stops the previous one.

Instructions

Play an audio or video file on this computer's speakers (for example a clip you just generated). Returns right away while it plays; a new play stops the previous one. Set stop to just stop playback. Free.

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

Input Schema

NameRequiredDescriptionDefault
stopNoStop whatever is playing instead.
input_pathNoFile to play: a path in the input or output folder, or a tapra://output/... resource.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover safety (readOnly, non-destructive, idempotent, closed-world), but the description adds real behavioral context beyond them: it returns immediately while playback continues asynchronously, a new play preempts the previous one, and playback can be interrupted via stop. The 'Free' note is a useful cost disclosure not present in annotations. It does not explain error behavior for invalid paths, but the added context is substantial.

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?

Three short sentences, front-loaded with the action and target, then async/preemption semantics, then the stop escape hatch and cost. The 'Free.' fragment is terse but carries distinct information; nothing is redundant.

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 only two optional parameters, no output schema, and rich annotations, the description covers what an agent needs: target, non-blocking behavior, preemption, and cancellation. Only edge cases (invalid path, whether video is audio-only) are left unspecified, which is a minor gap for a playback utility.

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 100%, so both parameters are already documented, including the tapra://output/... resource form. The description only adds the precedence nuance that stop halts current playback ('Set stop to just stop playback'), which the schema's 'Stop whatever is playing instead' nearly covers already. Baseline 3 is appropriate.

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?

Specific verb + resource + medium: 'Play an audio or video file on this computer's speakers', which distinguishes it from generation siblings like text_to_speech or create_voiceover. The parenthetical 'a clip you just generated' hints at the typical upstream tool, but no sibling is named explicitly.

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?

The phrase 'for example a clip you just generated' implies when to reach for it (after a generation step), and 'Free' signals it costs no credits versus paid siblings like text_to_speech. However, there are no explicit when-not conditions or named alternatives.

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