The MCP server currently still exposes the legacy
evals tool.
Use it for now to write criteria; the assert argument accepts a JSON-encoded
assertion spec (see Evals legacy notes). A
dedicated criteria tool that accepts the structured assertion object is
planned.Actions (planned)
| Action | Description |
|---|---|
list | List all criteria for a task |
create | Create a new criterion |
get | Get a criterion by ID |
update | Update a criterion |
delete | Delete a criterion |
Parameters
list
| Parameter | Type | Required | Description |
|---|---|---|---|
taskId | string | yes | Task ID to list criteria for |
create
| Parameter | Type | Required | Description |
|---|---|---|---|
taskId | string | yes | Task ID to attach the criterion to |
label | string | yes | Short human-readable label |
assertion | object | yes | Typed assertion spec. See Criteria API |
weight | number | no | Relative weight (default 1) |
axis | string | no | Optional scoring axis |
inputEntityId | string | no | Optional DatasetEntity ID the criterion is scoped to |
get
| Parameter | Type | Required | Description |
|---|---|---|---|
id | string | yes | Criterion ID |
update
| Parameter | Type | Required | Description |
|---|---|---|---|
id | string | yes | Criterion ID |
label | string | no | Updated label |
assertion | object | no | Updated assertion spec |
weight | number | no | Updated weight |
axis | string | no | Updated axis |
inputEntityId | string | no | Updated scoped DatasetEntity ID |
delete
| Parameter | Type | Required | Description |
|---|---|---|---|
id | string | yes | Criterion ID |