Ausca

Mint artifact download access

ausca_artifact_access

Idempotent

Return an idempotent, short-lived download URL for one verified artifact this service holds, including a result artifact named by a succeeded invocation's output_artifact. HTTP sends no request body, not even an empty JSON object; artifact_uri is the URL path parameter and Idempotency-Key is a header. The MCP tool instead takes artifact_uri and idempotency_key as tool arguments. The URL expires after at most 60 seconds. The immutable artifact reference is the only authority; verify downloaded bytes against the returned content digest.

Input Schema

Name	Required	Description	Default
`artifact_uri`	Yes
`idempotency_key`	Yes

Output Schema

Name	Required	Description	Default
`status`	Yes
`artifact`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed10 schema fields changedOct 25, 2026

removedInput schema / $defs / ArtifactRef

Removed value: -{
-  "description": "Opaque artifact reference minted by artifact commitment. Relay it unchanged; its form is not part of the contract.",
-  "maxLength": 512,
-  "minLength": 1,
-  "type": "string"
-}

addedInput schema / $defs / ArtifactUri

Added value: +{
+  "description": "Opaque artifact reference minted by artifact commitment. Relay it unchanged; its form is not part of the contract.",
+  "maxLength": 512,
+  "minLength": 1,
+  "type": "string"
+}

removedInput schema / properties / artifact_ref

Removed value: -{
-  "$ref": "#/$defs/ArtifactRef"
-}

addedInput schema / properties / artifact_uri

Added value: +{
+  "$ref": "#/$defs/ArtifactUri"
+}

changedInput schema / required

Previous value: -[
-  "artifact_ref",
-  "idempotency_key"
-]New value: +[
+  "artifact_uri",
+  "idempotency_key"
+]

removedOutput schema / $defs / ArtifactAccess / properties / artifact_ref
```
Removed value: -{
-  "$ref": "#/$defs/ArtifactRef"
-}
```
addedOutput schema / $defs / ArtifactAccess / properties / artifact_uri
```
Added value: +{
+  "$ref": "#/$defs/ArtifactUri"
+}
```

changedOutput schema / $defs / ArtifactAccess / required

Previous value: -[
-  "artifact_ref",
-  "content_digest",
-  "media_type",
-  "size_bytes",
-  "created_at",
-  "download_url",
-  "expires_at"
-]New value: +[
+  "artifact_uri",
+  "content_digest",
+  "media_type",
+  "size_bytes",
+  "created_at",
+  "download_url",
+  "expires_at"
+]

removedOutput schema / $defs / ArtifactRef

Removed value: -{
-  "description": "Opaque artifact reference minted by artifact commitment. Relay it unchanged; its form is not part of the contract.",
-  "maxLength": 512,
-  "minLength": 1,
-  "type": "string"
-}

addedOutput schema / $defs / ArtifactUri

Added value: +{
+  "description": "Opaque artifact reference minted by artifact commitment. Relay it unchanged; its form is not part of the contract.",
+  "maxLength": 512,
+  "minLength": 1,
+  "type": "string"
+}

Changed8 schema fields changedSep 18, 2026
- addedInput schema / $defs / ArtifactRef / description
```
Added value: +"Opaque artifact reference minted by artifact commitment. Relay it unchanged; its form is not part of the contract."
```
- addedInput schema / $defs / ArtifactRef / maxLength
```
Added value: +512
```
- addedInput schema / $defs / ArtifactRef / minLength
```
Added value: +1
```
- removedInput schema / $defs / ArtifactRef / pattern
```
Removed value: -"^runx:artifact:sha256:[a-f0-9]{64}$"
```
- addedOutput schema / $defs / ArtifactRef / description
```
Added value: +"Opaque artifact reference minted by artifact commitment. Relay it unchanged; its form is not part of the contract."
```
- addedOutput schema / $defs / ArtifactRef / maxLength
```
Added value: +512
```
- addedOutput schema / $defs / ArtifactRef / minLength
```
Added value: +1
```
- removedOutput schema / $defs / ArtifactRef / pattern
```
Removed value: -"^runx:artifact:sha256:[a-f0-9]{64}$"
```
AddedSep 7, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Goes beyond annotations by disclosing the 60-second URL expiry, that the operation is idempotent, and that downloaded bytes should be verified against the returned content digest. It also explains the transport distinction (no HTTP body; artifact_uri as path parameter, Idempotency-Key as header). This is meaningful behavioral context for a non-read-only, open-world 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?

Four sentences that are front-loaded with the core purpose, then transport, expiry, and verification detail. Dense but mostly earns its space; the HTTP-body clause is slightly pedantic but prevents a real misuse case.

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?

An output schema exists, so return values need not be explained, and the description covers expiry, idempotency, and integrity verification. The remaining gap is parameter-level detail (idempotency key constraints), but overall it is sufficient for correct invocation.

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 description coverage is reported as 0%, so the description must carry the burden; it does clarify that artifact_uri is an opaque, immutable reference relayed unchanged and that idempotency_key maps from an HTTP header into a tool argument. However, it never addresses the idempotency_key's format or 16-character minimum, nor when a key should be reused, leaving gaps the schema does not fill.

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 specific verb and resource: 'Return an idempotent, short-lived download URL for one verified artifact this service holds,' and scopes it to a single artifact including result artifacts from a succeeded invocation. It does not explicitly contrast with any sibling tool, but the operation is unambiguous and clearly distinct from the inbox/browser/invocation siblings.

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?

Implies the usage context by tying the artifact to a 'succeeded invocation's output_artifact,' so an agent can infer this is the post-success download step. There is no explicit when-not guidance or named alternative, leaving the selection logic to inference.

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

All Ausca tools Inspect

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.