Skip to main content
Glama
Sign In

Sats4AI - Bitcoin-Powered AI Tools

by io.github.cnghockey
OverviewDiscussionsAdmin

get_job_result

Read-onlyIdempotent

Retrieve the final output of a completed async job. Call ONLY after check_job_status returns status='COMPLETED' — calling on a job that has not completed returns an error. Returns JSON whose shape depends on jobType: video/video-image → { videoUrl, duration }; image-3d → { modelUrl } (GLB format); transcription → { text, language, segments, srt, vtt } (a result too large for one reply comes back without segments, srt and vtt, with resultTruncated, omitted and fullResultUrl: a free link to the whole result); epub-audiobook → { url, annexeUrl, totalChapters, completedChapters } (annexeUrl is a companion PDF of equations, tables, addresses, keys and hashes the narration replaces with a spoken marker; null when the book had none); ai-call → { transcript, duration, summary }. A video or 3D job whose payment was refunded returns error_code RESULT_NOT_AVAILABLE, unless you pass its paymentId: the payer then gets the pending refund (error_code L402_REFUND_ISSUED). An audiobook whose payment was refunded also returns RESULT_NOT_AVAILABLE, with no link: claim the refund at /recover with the payment ID. A web 3D purchase not yet collected on its own page also returns RESULT_NOT_AVAILABLE. All URLs are temporary (valid ~1 hour) — download immediately. This tool is free and does not require payment. Do NOT use for synchronous tools — those return results directly.

Input Schema

NameRequiredDescriptionDefault
jobTypeYesMust match the async tool: video=generate_video, video-image=animate_image, image-3d=generate_3d_model, transcription=transcribe_audio, epub-audiobook=epub_to_audiobook, ai-call=ai_call. video-fal-standard/video-fal-pro = the fallback jobType generate_video returns when the primary video model is at capacity.
paymentIdNoThe paymentId that bought this job. On a failed or refunded job the refund is opened either way; the claim link (lnurl_withdraw / refund_secret) is returned only when this matches — or call check_payment_status(paymentId).
requestIdYesThe requestId returned by the original async tool — same ID used with check_job_status

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / paymentId / description
      Previous value: -"The paymentId that bought this job. On a failed job the refund is opened either way; the claim link (lnurl_withdraw / refund_secret) is returned only when this matches — or call check_payment_status(paymentId)."New value: +"The paymentId that bought this job. On a failed or refunded job the refund is opened either way; the claim link (lnurl_withdraw / refund_secret) is returned only when this matches — or call check_payment_status(paymentId)."
  2. Changed1 schema field changed
    • changedInput schema / properties / jobType / description
      Previous value: -"Must match the async tool: video=generate_video, video-image=animate_image, image-3d=generate_3d_model, transcription=transcribe_audio, epub-audiobook=epub_to_audiobook, ai-call=ai_call. video-fal-standard/video-fal-pro = the FAL fallback jobType generate_video returns when Replicate is at capacity."New value: +"Must match the async tool: video=generate_video, video-image=animate_image, image-3d=generate_3d_model, transcription=transcribe_audio, epub-audiobook=epub_to_audiobook, ai-call=ai_call. video-fal-standard/video-fal-pro = the fallback jobType generate_video returns when the primary video model is at capacity."
  3. Changed1 schema field changed
    • addedInput schema / properties / paymentId
      Added value: +{
+  "description": "The paymentId that bought this job. On a failed job the refund is opened either way; the claim link (lnurl_withdraw / refund_secret) is returned only when this matches — or call check_payment_status(paymentId).",
+  "type": "string"
+}
  4. Changed1 schema field changed
    • changedInput schema / properties / jobType / enum
      Previous value: -[
-  "video",
-  "video-image",
-  "video-fal-standard",
-  "video-fal-pro",
-  "image-3d",
-  "transcription",
-  "transcribe-translate",
-  "epub-audiobook",
-  "ai-call"
-]New value: +[
+  "video",
+  "video-image",
+  "video-fal-standard",
+  "video-fal-pro",
+  "image-3d",
+  "transcription",
+  "transcribe-translate",
+  "translate-epub",
+  "epub-audiobook",
+  "ai-call"
+]
  5. Changed1 schema field changed
    • changedInput schema / properties / jobType / enum
      Previous value: -[
-  "video",
-  "video-image",
-  "video-fal-standard",
-  "video-fal-pro",
-  "image-3d",
-  "transcription",
-  "epub-audiobook",
-  "ai-call"
-]New value: +[
+  "video",
+  "video-image",
+  "video-fal-standard",
+  "video-fal-pro",
+  "image-3d",
+  "transcription",
+  "transcribe-translate",
+  "epub-audiobook",
+  "ai-call"
+]
  6. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Despite readOnly/idempotent annotations already covering safety, the description adds substantial behavioral context: per-jobType result shapes, truncation fallback with fullResultUrl, temporary ~1h URL validity, refund error codes (RESULT_NOT_AVAILABLE, L402_REFUND_ISSUED), and refund-claim flow via /recover. This goes well beyond what the annotations provide.

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?

Front-loaded with the core rule and prerequisite, then organized by jobType. It is dense and long, with some redundancy in refund scenarios, but nearly every sentence carries actionable information for correct invocation.

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 no output schema, the description carries the full burden of explaining return values, and it enumerates the shape per jobType, truncation handling, and refund cases. For a 3-param idempotent read tool, nothing an agent needs is missing.

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?

Schema coverage is 100%, so baseline would be 3, but the description adds real meaning: it maps jobType values to the output shapes they produce and explains the paymentId refund-claim behavior. It does not restate the enum-to-tool mapping already in the schema, but contributes useful conditional logic around paymentId.

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 precise verb+resource: retrieve the final output of a completed async job, and scopes it by naming the prerequisite sibling check_job_status and excluding synchronous tools. An agent can distinguish it from check_job_status and await_result without inspecting any 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?

Explicit when-to-use ('Call ONLY after check_job_status returns status=COMPLETED'), what happens when misused (error), and an exclusion ('Do NOT use for synchronous tools'). This is a complete routing rule with no inference required.

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

All Sats4AI - Bitcoin-Powered AI Tools toolsInspect
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