Slice

Get a transcription

transcription_status

Read-onlyIdempotent

Use this when transcribe_audio returned status "processing", to check whether the transcript is finished and get its text. Pass the transcription_id it returned. Call it again after a short wait while the status is still "processing". Only answers in the conversation (or Slice account) that started the transcription. Do not use to start a transcription; use transcribe_audio.

Input Schema

Name	Required	Description	Default
`transcription_id`	Yes	The transcription_id transcribe_audio returned.

Output Schema

Name	Required	Description
`status`	Yes
`message`	Yes
`language`	No	Detected language code, e.g. en.
`downloads`	No
`duplicate`	No	True when this is the transcript already made of the same file earlier: nothing new was started or counted. Do not send the file again.
`file_name`	No
`transcript`	No	The transcript in paragraphs, with speaker labels when there is more than one voice.
`word_count`	No
`results_url`	Yes	Page with the full transcript and downloads. No sign-in; share it only with people who should see the transcript.
`duration_minutes`	No
`transcription_id`	Yes	Pass to transcription_status or email_transcript.
`transcript_truncated`	No	True when only the first part is included here; the results page has all of it.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 22, 2026

addedOutput schema / properties / duplicate

Added value: +{
+  "description": "True when this is the transcript already made of the same file earlier: nothing new was started or counted. Do not send the file again.",
+  "type": "boolean"
+}

First observedOct 17, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Annotations already establish that this is a read-only, idempotent, non-destructive operation. The description adds useful behavior beyond that: polling semantics, access scoping to the conversation or Slice account that initiated the transcription, and the fact that the transcript text is returned once finished.

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?

The description is front-loaded with the primary usage condition, then polling guidance, then scope and exclusion. Every sentence carries actionable information, with 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?

With rich annotations, a complete single-parameter schema, and an output schema, the description supplies the remaining operational context an agent needs: when to call it, how to poll, what access scope applies, and which tool not to use. Nothing material is missing for correct invocation.

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 only one parameter and schema description coverage is 100%, so the schema already explains that transcription_id is the value returned by transcribe_audio. The description reinforces this but adds no syntax, format, or validation detail beyond the 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?

The description states a specific action: check whether a transcription started by transcribe_audio has finished and retrieve its text. It explicitly distinguishes itself from transcribe_audio, so an agent can route between the two tools without opening either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives the exact triggering condition (transcribe_audio returned status "processing"), explains how to poll (call again after a short wait while still processing), and explicitly says not to use it to start a transcription. The alternative, transcribe_audio, is named for the excluded case.

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

All Slice 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?