async-render-example v1.0.0A

Immutable. This exact content is served forever at /api/v1/blob/4be2a8da39c79a39.

---
name: async-render-example
description: "Example skill demonstrating async execution affinity. Use when you want to see how long-running tools surface as deferredHint=true in MCP tools/list."
license: MIT
compatibility: Python 3.7+
tags: [example, async, render]
dcc: python
version: "1.0.0"
search-hint: "async, long-running, render, deferred, timeout hint"
tools:
  - name: render_frames
    description: "Pretend to render a frame range. Long-running; the server surfaces `deferredHint: true` and `_meta.dcc.timeoutHintSecs`."
    execution: async
    timeout_hint_secs: 600
  - name: quick_status
    description: "Return the current (fake) render status. Fast, sync."
    execution: sync
---

# Async Render Example (issue #317)

This skill demonstrates the `execution` and `timeout_hint_secs` fields added
for issue #317. Tools are declared with either `execution: sync` (default)
or `execution: async`; the MCP server derives the `deferredHint` annotation
from this value and surfaces `timeout_hint_secs` under
`_meta.dcc.timeoutHintSecs` on the tool definition (never inside
`annotations`).

## Behaviour

- `render_frames` → `execution: async` + `timeout_hint_secs: 600`
  → `tools/list` entry gets `"annotations": { "deferredHint": true, ... }`
  and `"_meta": { "dcc": { "timeoutHintSecs": 600 } }`.
- `quick_status` → no `execution` field → default `Sync`
  → `"annotations": { "deferredHint": false, ... }` and no `_meta`.

## Script convention

Each script reads JSON parameters from stdin and writes a JSON result to
stdout — the standard dcc-mcp-core skill script contract.