dsh-tool-read-tiff

Configuration

The tool works with zero configuration (decode + convert + metadata only). To enable the one-shot visual description, configure the vision endpoint (Settings → 插件配置 → "TIFF reading", or a composition entry):

Key	Default	Meaning
baseURL	—	OpenAI-compatible endpoint root (e.g. https://dashscope.aliyuncs.com/compatible-mode/v1); trailing slashes stripped
model	—	Vision model id
apiKey	—	Inline key; prefer apiKeyEnv
apiKeyEnv	VISION_API_KEY	Environment-variable name for the API key (shared convention with the describe-image tool)
defaultPrompt	see source	Instruction used when a call omits its prompt
maxBytes	67108864	TIFF byte bound (local files and downloads alike)
maxOutputTokens	1024	Output-token cap sent to the vision model
timeoutMs	60000	Per-call vision request timeout
outputDir	— (temp dir for URLs)	Where converted PNGs go when the source is not a local file

Configured mount example (cordis.patch.yml / composition file):

- id: read-tiff
  name: 'dsh-tool-read-tiff'
  config:
    baseURL: https://dashscope.aliyuncs.com/compatible-mode/v1
    model: qwen-vl-max
    apiKey: !!js process.env.VISION_API_KEY

Usage

Point the tool at a TIFF and (optionally) give the vision model a precise instruction:

• "transcribe all text in this scanned fax"
• "extract the table as CSV"
• "describe the map features and projection"
• "what does the label in the corner say"

For multi-page files, call again with page: 1, page: 2, and so on; pages tells you how many there are. When no vision endpoint is configured, the tool still returns everything it decoded plus a convertedPath you can hand to the already-installed describe_image tool.