Crevio

start_chat

Destructive

Open a chat with the Crevio agent and queue a run, without waiting. Returns the run immediately — its chat_id is the conversation to continue with send_message. Follow the run with wait_for_run or get_run.

Input Schema

TableJSON Schema

Name	Required	Description
`speed`	No	faster thinks less, for simple jobs where latency matters more than depth; smarter (default) thinks it through.
`message`	Yes	What you want done, in natural language, with all the context needed — the agent does not see your conversation.
`approval_mode`	No	autonomous (default) acts without review; supervised pauses in needs_input for your approval before each gated write (pending_approval_ids) and otherwise finishes with its proposal; read_only forbids writes.
`idempotency_key`	No	Always pass one, unique to this request. Retrying with the same key within an hour returns the run the first call started instead of doing the job twice.

Output Schema

TableJSON Schema

Name	Required	Description
`id`	Yes
`object`	Yes
`result`	No
`reused`	No
`status`	Yes
`chat_id`	No
`summary`	No
`task_id`	Yes
`next_step`	No
`task_name`	No
`created_at`	Yes
`started_at`	No
`completed_at`	No
`error_message`	No
`wait_timed_out`	No	The wait ended first. The work is still running: follow it with the tool next_step names.
`credits_consumed`	No
`pending_approval_ids`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedSep 29, 2026

changedInput schema / properties / idempotency_key / description

Previous value: -"Retrying with the same key returns the run the first call started instead of starting another."New value: +"Always pass one, unique to this request. Retrying with the same key within an hour returns the run the first call started instead of doing the job twice."

changedInput schema / properties / message / description

Previous value: -"What you want done, in natural language."New value: +"What you want done, in natural language, with all the context needed — the agent does not see your conversation."

addedInput schema / properties / speed

Added value: +{
+  "description": "faster thinks less, for simple jobs where latency matters more than depth; smarter (default) thinks it through.",
+  "enum": [
+    "faster",
+    "smarter"
+  ],
+  "type": "string"
+}

addedOutput schema / properties / next_step
```
Added value: +{
+  "type": "string"
+}
```

addedOutput schema / properties / wait_timed_out

Added value: +{
+  "description": "The wait ended first. The work is still running: follow it with the tool next_step names.",
+  "type": "boolean"
+}

Changed1 schema field changedSep 24, 2026

changedInput schema / properties / approval_mode / description

Previous value: -"autonomous (default) acts without review; supervised pauses in needs_input for your review before finishing; read_only forbids writes."New value: +"autonomous (default) acts without review; supervised pauses in needs_input for your approval before each gated write (pending_approval_ids) and otherwise finishes with its proposal; read_only forbids writes."

Changed1 schema field changedSep 22, 2026

changedOutput schema / properties / status / enum

Previous value: -[
-  "pending",
-  "running",
-  "completed",
-  "failed",
-  "needs_input",
-  "timed_out",
-  "unknown"
-]New value: +[
+  "pending",
+  "running",
+  "completed",
+  "failed",
+  "needs_input",
+  "timed_out",
+  "unknown",
+  "skipped"
+]

Changed1 schema field changedSep 6, 2026

changedOutput schema / properties / status / enum

Previous value: -[
-  "pending",
-  "running",
-  "completed",
-  "failed",
-  "needs_input",
-  "timed_out"
-]New value: +[
+  "pending",
+  "running",
+  "completed",
+  "failed",
+  "needs_input",
+  "timed_out",
+  "unknown"
+]

Changed1 schema field changedSep 2, 2026

changedOutput schema / properties / status / enum

Previous value: -[
-  "pending",
-  "running",
-  "completed",
-  "failed",
-  "needs_input"
-]New value: +[
+  "pending",
+  "running",
+  "completed",
+  "failed",
+  "needs_input",
+  "timed_out"
+]

First observedAug 22, 2026

TDQS

A4.2/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare destructiveHint=false... rather openWorldHint=true and destructiveHint=true, which is unusual for a chat tool and the description does not reconcile it. What the description does add is genuinely useful: the non-blocking semantics, that a run is queued, and that the returned chat_id is the handle for continued conversation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences, front-loaded with the non-blocking contract and then the continuation handle. Every sentence carries information; nothing restates the tool name.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a queued, long-running, multi-mode operation with an output schema, the description covers the async contract and continuation path well enough to call it correctly. The remaining gap is the missing contrast with ask_crevio, which matters for selecting this tool over its blocking sibling.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so every parameter (speed, approval_mode, idempotency_key) is already documented in the schema with enum semantics. The description adds no parameter-level syntax or format beyond what the schema supplies, so baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb+resource ('Open a chat with the Crevio agent and queue a run') and immediately disambiguates via scope: it does not block, it returns the run. An agent can distinguish this from send_message, wait_for_run and get_run without opening a schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It names the follow-up paths explicitly ('continue with send_message', 'follow the run with wait_for_run or get_run'), which gives real routing guidance. However it never contrasts itself with the sibling ask_crevio, which is presumably the blocking counterpart, so the primary when-to-use choice is left to inference.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Crevio tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?