Skip to main content
Glama

TranscriptLab

Check transcript job

transcriptlab_get_job_status
Read-onlyIdempotent

Check whether a transcript job from transcriptlab_get_transcript has finished. Use it when that tool returned a job_id instead of a transcript. Returns status only, delivers no transcript, and spends no credits; once it reports done, read the text with transcriptlab_retrieve_transcript.

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": {
      "job_id": "<job_id>"
    },
    "name": "transcriptlab_get_job_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
job_idYesJob id returned by transcriptlab_get_transcript.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, but the description adds non-obvious operational facts: it delivers no transcript and spends no credits. It does not state polling cadence or whether status values are pending/failed/done, which would matter for a job-status tool.

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 purpose, then the trigger, then the behavioral caveats and next step. No sentence repeats the title or the schema, and nothing is padding.

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 single-parameter polling tool with no output schema, the description covers purpose, trigger, cost, non-delivery of content, and the next step. The only gap is that the set of possible status values and expected retry behavior are not described, which leaves the agent guessing about what 'done' looks like.

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 the job_id parameter is already documented in the schema with the same provenance ('returned by transcriptlab_get_transcript'). The description adds no format, validity-window, or reuse semantics beyond that, so the baseline 3 applies.

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 ('Check whether a transcript job ... has finished') and ties the tool to a named sibling, transcriptlab_get_transcript. It is clearly distinguishable from transcriptlab_retrieve_transcript, which the description identifies as the follow-up step for obtaining text.

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?

Gives an explicit trigger condition ('Use it when that tool returned a job_id instead of a transcript') and a follow-up route ('once it reports done, read the text with transcriptlab_retrieve_transcript'). The agent knows both when to enter this tool and where to go after it.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.