Skip to main content
Glama
Sign In

XBOSS

by kr.xdata
OverviewDiscussionsAdmin

작업 결과 다시 받기

xdata__job__result
Read-only

No credential or login required. Reads the result of a job this connection already started, again, from its job_id. Starts no new job, sends nothing to any institution and spends no usage tokens. Use it when a call timed out while the job kept running (the error's data carries the job_id and a ready result_tool_call), or when a download_url in artifacts[] has expired: every call signs fresh links that work for 15 minutes, and the files themselves are kept for 7 days after the job. If the job is still running it waits up to 60 seconds, then says so - call it again a little later. Give pack_run_id instead of job_id to read a pack result again (a pack result that carries artifacts[] has its pack_run_id); a pack that has not finished is reported as not finished - this tool does not advance it. For an anonymous result, keep its private recovery_receipt and send it with the original job_id or pack_run_id to xdata__job__result. It grants access to that result only, until the original file retention expires. Do not publish it. Losing it cannot be repaired by signing up. The receipt also works if the client later signs in; it does not grant access to other results. Without a receipt, results require the original account and lane.

Input Schema

NameRequiredDescriptionDefault
job_idNoThe job_id of an earlier call, exactly as returned (job_ followed by 26 characters) - in data.job_id of a timeout error, or in job_id of a result that carries artifacts[]. Give this or pack_run_id, not both.
pack_run_idNoThe pack_run_id of an earlier pack result, exactly as returned (prun_ followed by 26 characters). Give this or job_id, not both.
recovery_receiptNoFor an anonymous result, keep its private recovery_receipt and send it with the original job_id or pack_run_id to xdata__job__result. It grants access to that result only, until the original file retention expires. Do not publish it. Losing it cannot be repaired by signing up. The receipt also works if the client later signs in; it does not grant access to other results. Without a receipt, results require the original account and lane.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / maxProperties
      Previous value: -1New value: +2
    • addedInput schema / oneOf
      Added value: +[
+  {
+    "required": [
+      "job_id"
+    ]
+  },
+  {
+    "required": [
+      "pack_run_id"
+    ]
+  }
+]
    • addedInput schema / properties / recovery_receipt
      Added value: +{
+  "description": "For an anonymous result, keep its private recovery_receipt and send it with the original job_id or pack_run_id to xdata__job__result. It grants access to that result only, until the original file retention expires. Do not publish it. Losing it cannot be repaired by signing up. The receipt also works if the client later signs in; it does not grant access to other results. Without a receipt, results require the original account and lane.",
+  "maxLength": 2048,
+  "minLength": 1,
+  "type": "string"
+}
  2. Changed5 schema fields changed
    • addedInput schema / maxProperties
      Added value: +1
    • addedInput schema / minProperties
      Added value: +1
    • changedInput schema / properties / job_id / description
      Previous value: -"The job_id of an earlier call, exactly as returned (job_ followed by 26 characters) - in data.job_id of a timeout error, or in job_id of a result that carries artifacts[]."New value: +"The job_id of an earlier call, exactly as returned (job_ followed by 26 characters) - in data.job_id of a timeout error, or in job_id of a result that carries artifacts[]. Give this or pack_run_id, not both."
    • addedInput schema / properties / pack_run_id
      Added value: +{
+  "description": "The pack_run_id of an earlier pack result, exactly as returned (prun_ followed by 26 characters). Give this or job_id, not both.",
+  "pattern": "^prun_[0-9A-HJKMNP-TV-Z]{26}$",
+  "type": "string"
+}
    • removedInput schema / required
      Removed value: -[
-  "job_id"
-]
  3. Added

TDQS

A4.5/5.0
Behavior5/5

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

Beyond the readOnly/destructive annotations, it discloses that no tokens are spent, that fresh signed links last 15 minutes, that files persist 7 days, that the call blocks up to 60 seconds, and that a pack result is not advanced by this call. The recovery_receipt access model and its irrecoverability are also spelled out.

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?

The key constraint (no new job, no side effects) is front-loaded and every sentence is informative. It is somewhat long, and the receipt paragraph repeats schema content, which is the only waste.

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 timing, retention, blocking behavior, alternative identifier, and anonymous-access recovery for a read-only tool with no output schema. It does not describe the shape of the returned result beyond referencing artifacts[], which is a minor gap.

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 100% and the schema descriptions already explain job_id, pack_run_id and recovery_receipt in detail. The description's receipt paragraph duplicates the schema text verbatim rather than adding new semantics; the job_id/pack_run_id trade-off is also already in the schema. 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 ('reads the result of a job this connection already started, again, from its job_id') and explicitly negates the neighboring action ('Starts no new job, sends nothing...'). The agent can distinguish this retrieval tool from job-creating siblings without opening 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?

Gives concrete trigger conditions: a timed-out call whose error carries job_id/result_tool_call, or an expired download_url in artifacts[]. It also routes between job_id and pack_run_id and tells the agent what to do when the job is still running ('call it again a little later').

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

All XBOSS 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