Skip to main content
Glama
Sign In
MCP Yandex Voice

MCP Yandex Voice

by dimaanj
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Остановка / пауза воспроизведения

playback_control

Control audio playback of Yandex Voice responses. Stop or pause the current afplay WAV playback on macOS.

Instructions

Остановить или поставить на паузу текущее воспроизведение голоса (ответа Yandex Voice). Работает только на macOS; действует только для воспроизведения через afplay (WAV).

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

Input Schema

NameRequiredDescriptionDefault
actionYesstop — остановить, pause — остановить (возобновление не поддерживается)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4/5.0
Behavior3/5

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

No annotations provided, so description must cover behavior. It mentions constraints but omits edge cases (e.g., no current playback, multiple instances, state after pause). Adequate but not exhaustive.

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?

Two concise sentences: first states purpose, second adds constraints. No filler, front-loaded.

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?

For a simple tool with one parameter and no output schema, description covers key constraints. Lacks handling of error states, but acceptable given tool simplicity.

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%, with enum values explained. Description repeats the action names without adding new meaning, meeting baseline but not exceeding.

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?

Description clearly states the action (stop/pause) and resource (current playback of Yandex Voice response). Sibling tools like play_sound and speak_response are distinct, so no ambiguity.

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?

Explicitly specifies platform (macOS) and audio source (afplay/WAV) constraints, guiding when to use. Lacks explicit contrast with siblings but sufficient for differentiation.

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