Skip to main content
Glama
Sign In
voicesmith

voicesmith

by fergo5002
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Job Status

job_status

Check the progress and result of a speech render started by speak, so you can poll long-running jobs and confirm when audio output is ready.

Instructions

Progress and result of a render started by speak.

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

Input Schema

NameRequiredDescriptionDefault
job_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It does not disclose whether a call blocks or returns immediately, whether repeated polling is expected, what terminal states exist, or whether job ids expire — all critical for a status-polling tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single short sentence that front-loads the return payload (progress and result) and the originating tool. No filler, though the terseness contributes to the behavioral gaps noted elsewhere.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The output schema exists, so return values need not be explained, and the link to speak is established. Still missing are polling semantics, terminal/error states, and any note on job id validity, which an agent needs to use this tool correctly.

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 coverage is 0%, so the single job_id parameter is undocumented. The description partially compensates by implying the id comes from speak's render request, but it does not state the id's format, lifetime, or whether reusing an id from another source is valid.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a concrete resource (a render job) and what it returns (progress and result), and anchors it to the sibling tool that creates the job ('started by speak'). An agent can distinguish it from speak without opening the schema, though the verb is implicit rather than stated.

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

Usage Guidelines3/5

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

'started by speak' implies this is the follow-up call for a job created by speak, giving useful context. However, it never says when to call (immediately after speak? repeatedly to poll?) or whether there is any alternative path for retrieving render results.

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