DevTune MCP

devtune_quote_agent_picks_test

Read-only

Quote a paid Agent Picks test, an Action re-test or one run of a schedule, in credits, without spending anything. Pass test options (preset quick or cell, runs_per_cell, scope) for a test, action_id for a re-test of a completed or live Action (no other options), or schedule (daily, weekly or monthly) for a schedule. Returns estimate {expected, high, runs} in credits (high reserves every planned run; in a full test, or a test at 8 runs per cell without a preset, a cell stops after 4 runs that agree, which expected assumes and which charges only the runs that ran; a cell re-run at 8 does not stop early), excluded_agents (saved agents the plan does not include), quote_token and expires_at (15 minutes). A test quote also returns test_id, the id the start will use: follow it with devtune_get_agent_picks_test. Pass quote_token to devtune_start_agent_picks_test or devtune_enable_agent_picks_schedule; it works once and only for this connection and project. Refusals carry a reason, including test_in_progress, no_settings, job_incomplete, agent_not_in_plan, runner_disabled, customer_requests_off, action_not_shipped, baseline_unavailable, baseline_changed, invalid_test_options and unpriced_model. Requires visibility.read and Agent Picks.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "devtune_quote_agent_picks_test"
  }
}

Input Schema

Name	Required	Description
`scope`	No
`setup`	No	The Agent Picks setup to use: its id or its category slug. Optional while the project has one setup. With several, omitting it is refused as agent_picks_setup_required, and a setup the project does not have as agent_picks_setup_not_found; both list the project setups in details.setups (id, category_slug, category_name). The response echoes the setup used as setup {id, category_slug}.
`preset`	No
`schedule`	No
`action_id`	No
`runs_per_cell`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 9, 2026

changedInput schema / properties / scope / properties / agent_models / items / properties / agent / enum

Previous value: -[
-  "claude_code",
-  "codex",
-  "opencode",
-  "pi"
-]New value: +[
+  "claude_code",
+  "codex",
+  "opencode",
+  "pi",
+  "muse_code"
+]

Changed1 schema field changedOct 31, 2026

addedInput schema / properties / setup

Added value: +{
+  "description": "The Agent Picks setup to use: its id or its category slug. Optional while the project has one setup. With several, omitting it is refused as agent_picks_setup_required, and a setup the project does not have as agent_picks_setup_not_found; both list the project setups in details.setups (id, category_slug, category_name). The response echoes the setup used as setup {id, category_slug}.",
+  "maxLength": 200,
+  "minLength": 1,
+  "type": "string"
+}

Changed1 schema field changedOct 27, 2026

changedInput schema / properties / scope / properties / intents / items / enum

Previous value: -[
-  "add",
-  "recommend",
-  "hosted"
-]New value: +[
+  "add",
+  "recommend",
+  "hosted",
+  "improve"
+]

AddedOct 25, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, but the description adds real value beyond them: no credits are spent, quote_token is single-use and bound to this connection and project, it expires in 15 minutes, and refusals return enumerated reasons (test_in_progress, baseline_changed, unpriced_model, etc.). It also explains the expected-vs-high billing model and the 4-run agreement cutoff, though that sentence is dense enough that a reader may need to re-read it.

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

Conciseness3/5

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

It is front-loaded and every section carries information, but it is delivered as one dense block with long parenthetical clauses, especially the run-count/early-stop explanation and the 11-code refusal list. The content earns its place; the packaging makes it harder to parse than it needs to be.

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?

There is no output schema, yet the description fully specifies the return shape ({expected, high, runs}, excluded_agents, quote_token, expires_at, plus test_id for tests) and the auth requirements (visibility.read and Agent Picks). Combined with token lifecycle and refusal reasons, an agent has everything needed to call and consume 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 description coverage is only 17%, so the description carries most of the burden. It does explain preset (quick or cell), runs_per_cell, action_id exclusivity and schedule values, but it never describes the nested scope object (intents, request_ids, agent_models, environment_ids) and only mentions setup indirectly, leaving meaningful ambiguity for a 6-parameter tool with a nested object.

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 (Quote), a specific resource (Agent Picks test / Action re-test / one schedule run), and the outcome (credits, no spend). The three supported modes are enumerated up front, which lets an agent distinguish it from devtune_start_agent_picks_test, which actually spends.

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?

Gives explicit mode-selection rules: test options for a test, action_id alone for a re-test of a completed or live Action, schedule for a schedule. It also names the downstream tools to call (devtune_get_agent_picks_test for the test_id, devtune_start_agent_picks_test / devtune_enable_agent_picks_schedule for the token), leaving little to inference.

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

All DevTune MCP 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?