Skip to main content
Glama
Sign In
@speechweave/mcp

@speechweave/mcp

Official
by speechweave
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Get job status

get_job_status

Retrieve the current status of a transcription job and get the transcript upon completion. Poll until the job finishes, fails, or is cancelled.

Instructions

Fetch the current status of a transcription job (and transcript when completed). Poll until status is completed, failed, or cancelled.

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

Input Schema

NameRequiredDescriptionDefault
job_idYesJob id returned by a create or wait-first transcription tool.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

A4.2/5.0
Behavior3/5

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

Describes basic behavior (fetch status, include transcript when done, poll). No annotations exist, so description carries full burden. It doesn't mention error handling, rate limits, or authentication needs, but the core read-only behavior is clear.

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 that front-load the primary function and include essential usage instruction (poll). No unnecessary words.

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?

Given the tool's simplicity (one parameter, no output schema), the description adequately covers its purpose and usage pattern. Could be slightly more explicit about return value, but polling instruction compensates.

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?

Single parameter job_id has schema description 'Job id returned by a create or wait-first transcription tool.' The tool description adds context that the id comes from specific tools, which is valuable 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?

Clearly states it fetches job status and transcript when completed, with specific verb 'Fetch' and resource 'status of a transcription job'. Distinguishes from sibling tools (transcribe, start, cancel) by focusing on monitoring/polling.

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 says to poll until completed/failed/cancelled, guiding usage as a polling mechanism. Does not explicitly mention when not to use, but the polling instruction implies it's for ongoing jobs.

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