classdesk

Vorlesetext vorlesen lassen

speak_support_item

Lässt den gespeicherten Vorlesetext-Entwurf eines Audio-Bausteins von ElevenLabs vorlesen und bindet die MP3 ein (kostet Vorlese-Kontingent). NUR aufrufen, nachdem die Lehrkraft genau diesen Text und die Stimme im Chat gesehen und ausdrücklich bestätigt hat. text und voice = der bestätigte Text, Zeichen für Zeichen wie im Entwurf, und die bestätigte Stimme – weicht eins ab, wird nichts vorgelesen.

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": {
      "package_id": "<package_id>",
      "item_id": "<item_id>",
      "text": "<text>",
      "voice": "<voice>"
    },
    "name": "speak_support_item"
  }
}

Input Schema

Name	Required	Description
`text`	Yes	der von der Lehrkraft bestätigte Vorlesetext (muss dem Entwurf entsprechen)
`voice`	Yes	die von der Lehrkraft bestätigte Stimme (muss dem Entwurf entsprechen)
`item_id`	Yes
`package_id`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 30, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Adds substantial behavior beyond the annotations: external ElevenLabs processing, quota cost, MP3 embedding, and the no-op outcome when text or voice deviates. This is exactly the operational context an agent needs before invoking a costly external mutation.

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 efficient sentences: purpose and cost first, then the hard precondition, then the parameter-matching rule and consequence. There is no filler and the gating condition is 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?

Covers the side effect, cost, precondition, and mismatch behavior for a mutation tool with no output schema. It still leaves package_id/item_id semantics and result details somewhat implicit, so it is strong but not fully complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema already documents text and voice, but the description adds the crucial constraint that both must match the confirmed draft character-for-character and that a mismatch prevents speech. package_id and item_id remain undocumented in both schema and description, though 'eines Audio-Bausteins' hints at their role.

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 action: having the saved read-aloud draft of an audio component spoken by ElevenLabs and embedding the MP3. This is clearly distinct from sibling tools such as update_support_item or add_support_item, and it names the resource affected.

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 gates invocation on the teacher having seen and explicitly confirmed the exact text and voice, and states that a mismatch prevents reading. It does not name an alternative or preparatory tool to use when confirmation is missing, so it falls short of full routing guidance.

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

All classdesk 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.

Resources

Need Help?