Skip to main content
Glama
Sign In
Thrixel MCP Server

Thrixel MCP Server

Official
by thrixel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Check a Thrixel job

thrixel_job_status

Check if a submitted job has finished. Only needed for jobs submitted with wait=false, as other tools wait and return the finished asset.

Instructions

Check whether a job has finished. Only needed for jobs submitted with wait=false - every other tool already waits and returns the finished asset.

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": {
      "submission_id": "<submission_id>"
    },
    "name": "thrixel_job_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
submission_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

A3.9/5.0
Behavior3/5

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

No annotations provided, so description carries full burden. It states purpose but does not disclose return behavior, error handling, or polling semantics. Adequate but could be more transparent.

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 succinct sentences, front-loaded with purpose, no wasted 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?

Covers core purpose and usage context well; output schema exists to explain return values, so lack of return info is acceptable. Missing parameter description is a minor gap.

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

Parameters1/5

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

Schema has 0% description coverage and description adds no meaning to the sole parameter 'submission_id'—does not explain what it is or where to get it.

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?

Description clearly states verb 'check' and resource 'job status', and distinguishes from siblings by noting it's only for jobs with wait=false.

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?

Explicitly specifies when to use (only for jobs with wait=false) and implies when not to use (other tools already wait and return finished asset).

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