Understanding capabilities

Tools, Vision, Reasoning and Structured tags and their verification limits.

On this page

What tags mean

Tag	Meaning
Tools / Function calling	Tool calls; agents need confirmed support
Vision	Image input
Reasoning	Reasoning may consume output budget; model-specific
Structured	Structured output; use a supported schema
Chat / Code	Usage categories, not a guarantee of all features

A missing tag is not proof of non-support. A 400 or absent tool_calls alone is inconclusive: parameters, schema, prompting or context may be responsible. Check catalog details first; a small validation call may incur charges.

curl https://macdecloud.com/v1/chat/completions \
  -H "Authorization: Bearer $DECLOUD_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
  "model": "deepseek/deepseek-chat",
  "messages": [
    {
      "role": "user",
      "content": "Use read_file to read /tmp/a.txt"
    }
  ],
  "tools": [
    {
      "type": "function",
      "function": {
        "name": "read_file",
        "description": "Read a file",
        "parameters": {
          "type": "object",
          "properties": {
            "path": {
              "type": "string"
            }
          },
          "required": [
            "path"
          ]
        }
      }
    }
  ]
}'

Related documentation

400 · Troubleshooting tool callsupstream_bad_request means the upstream rejected the request. Unsupported tools are one possible cause; parameters, tool schema, content format or excessive context may also trigger it.200 · Success without textNull content is not always an error: a tool reply may contain only tool_calls. finish_reason length indicates an output limit, which reasoning may consume on some models. Not all empty replies have this cause.Model catalogThe public plaza and authenticated catalog; where to find prices and capabilities.