Crevio

ask_crevio

Delegate a job to the Crevio agent and wait for the result. Starts a run that works your account through the Crevio API (products, customers, orders, email, socials, sites, research), waits up to timeout_seconds, and returns the run with the agent's final reply in result. For anything longer, use start_task and wait_for_run.

Input Schema

TableJSON Schema

Name	Required	Description
`message`	Yes	What you want done, in natural language.
`approval_mode`	No	autonomous (default) acts without review; supervised pauses in needs_input for your review before finishing; read_only forbids writes.
`idempotency_key`	No	Retrying with the same key returns the run the first call started instead of starting another.
`timeout_seconds`	No	How long to wait for the run to settle before returning (default 60, max 90). On wait_timed_out, call wait_for_run with the run id.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`id`	Yes
`object`	Yes
`result`	No
`reused`	No
`status`	Yes
`chat_id`	No
`summary`	No
`task_id`	Yes
`task_name`	No
`created_at`	Yes
`started_at`	No
`completed_at`	No
`error_message`	No
`credits_consumed`	No
`pending_approval_ids`	No

TDQS

A4.5/5.0

Behavior4/5

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

It discloses that the tool executes through the Crevio API across several domains, waits synchronously, and returns the agent's final reply in result. Annotations already cover readOnly/destructive hints, so the added run lifecycle context is meaningful, though it could mention idempotency behavior explicitly.

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?

Two sentences, front-loaded with the core action and then a concise fallback for longer jobs. Every phrase earns its place without repetition.

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

Completeness5/5

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

Given the complete schema descriptions, the enclosing annotation hints, the output schema, and the explicit timeout fallback to wait_for_run, nothing critical is missing for an agent to decide when and how to call this tool.

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 coverage is 100%, so all four parameters already have descriptions. The description reinforces timeout_seconds behavior and the result field, but adds little beyond what the schema provides, so the baseline of 3 is appropriate.

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?

The description states a specific verb and resource: delegate a job to the Crevio agent, start a run, wait up to timeout_seconds, and return the final reply in result. It also names the sibling alternative (start_task and wait_for_run), so an agent can distinguish it from related run-management tools.

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

Usage Guidelines5/5

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

It explicitly says when to use this tool versus the alternative: 'For anything longer, use start_task and wait_for_run.' This gives clear routing guidance beyond just describing the action.

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

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4/5.0

Disambiguation5/5

Each tool maps to a distinct resource-action pair: REST execution, endpoint discovery, chat/run lifecycle, approvals, and identity. Even similar tools like get_run and wait_for_run are clearly separated by blocking vs. non-blocking behavior.

Naming Consistency4/5

Most tools follow a clear snake_case verb_noun pattern (get_run, list_chats, send_message, cancel_run). Minor deviations like api_execute, api_search, ask_crevio, and whoami keep the set readable but prevent a perfect consistency score.

Tool Count5/5

Fourteen tools is within the well-scoped range and each tool has a meaningful role across API access, run management, chat interaction, approvals, and account identity. No obvious bloat or redundant duplicates.

Completeness4/5

The generic api_execute tool provides broad REST API coverage, and run/chat lifecycle tools are nearly complete. The ask_crevio description references a start_task tool that does not exist, though start_chat offers a workaround for launching runs without waiting.

Resources

Need Help?