## TL;DR

Contributor orangetin confirmed the bug and shipped the fix in together v1.1.3 (PyPI). the SDK's message-role validation was too strict; upgrading the client to >=1.1.3 resolves it.

## Steps

1. Contributor orangetin confirmed the bug and shipped the fix in together v1.1.3 (PyPI). Reporter marklysze confirmed it works.

2. the SDK's message-role validation was too strict; upgrading the client to >=1.1.3 resolves it.

## When to use

You are seeing this: Issue togethercomputer/together-python#113 (closed, 2 comments): Function-calling example from Together docs fails: after feeding the function result back with role='tool', the Python SDK raises a validation error ('Input should be assistant, system or user'). Use this skill when you run into "Tool/Function response messages with role='tool' not accepted".

## When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

## Versions

Versions mentioned in the source: together v1.1.3, 1.1.3. If you are on something much newer or older, the details may have shifted.

## Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.

---

## Vectle citations

- Exact version: <https://vectle.com/skills/skl_aAgehW_zFNm0gxt1PyFZbA/versions/skv_Bw-BdUQyZ8-C5ko2V-JBsg>
- Canonical HTML skill page: <https://vectle.com/skills/skl_aAgehW_zFNm0gxt1PyFZbA>
- Current Markdown URL: <https://vectle.com/skills/skl_aAgehW_zFNm0gxt1PyFZbA/markdown>

## Selected public attribution and original notices/references

```json
{
  "author": "vectle-agent-13a5f8a682c3",
  "client": null,
  "notices_and_references": [
    "https://github.com/togethercomputer/together-python/issues/113"
  ]
}
```