DevTune MCP

devtune_get_agent_picks_schedule

Read-onlyIdempotent

Read the project test cadence, next UTC run, newest skipped period with reason, action and action_href, and the current paid-test estimate per run and for the next calendar month against plan credits. Every plan can schedule. Requires Agent Picks and visibility.read. last_skipped is null when the cadence is off or the newest period was not skipped. Reasons include insufficient_credits, permission_changed, no_settings, estimate_changed and agent_not_in_plan (the Agent Picks plan of the account includes none of the saved agents; action view_plans links to billing); follow action_href to recover. test_in_flight and unavailable have null action and action_href because nothing needs fixing. Read this estimate before setting a schedule.

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_get_agent_picks_schedule"
  }
}

Input Schema

Name	Required	Description	Default
`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}.

Schema Changelog

Changes observed during successful MCP inspections.

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"
+}

AddedOct 15, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Annotations already cover the read-only/idempotent safety profile, and the description adds substantial context beyond them: permission requirements, the null semantics of last_skipped, the null action/action_href for test_in_flight and unavailable, the meaning of each skip reason, and that view_plans links to billing.

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

Conciseness4/5

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

Front-loaded with the core purpose and packed with substance; nearly every clause earns its place. The dense parenthetical enumeration of skip reasons is long but pays off in interpretation guidance, though it slightly burdens scanning.

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, so the description must describe return values — and it does, covering cadence, next UTC run, last_skipped with reason/action/action_href, and per-run plus next-month cost estimates against plan credits, along with auth prerequisites.

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% and the single optional `setup` parameter is documented exhaustively in the schema, including error codes and the response echo. The description adds nothing about that parameter, so the 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?

The description opens with a precise verb+resource pair ('Read the project test cadence, next UTC run...') and enumerates the exact fields returned, so an agent can distinguish it from mutating siblings like devtune_disable_agent_picks_schedule or devtune_update_agent_picks_settings without opening any 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 states prerequisites ('Requires Agent Picks and visibility.read', 'Every plan can schedule') and a concrete workflow rule: 'Read this estimate before setting a schedule.' It does not name the specific setup/update tool to call next or state when this read is unnecessary, so it stops short of full alternative routing.

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?