DevTune MCP

devtune_clear_agent_picks_setup

DestructiveIdempotent

Remove one of the project's Agent Picks setups. Its tests and results stay readable, its schedule stops, and its suggested Actions nobody has accepted are removed. With several setups, pass setup; without it the call is refused as agent_picks_setup_required. Removing the last setup leaves the project with none until one is saved again. Removing a setup that is already gone is a no-op. Requires actions.write and Agent Picks. The OAuth member, or the member who created the API key, needs project management rights.

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

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 25, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Annotations already flag destructiveHint=true and idempotentHint=true, yet the description adds real detail beyond them: which artifacts survive, that the schedule stops, that unaccepted suggested Actions are deleted, the consequence of removing the last setup, and the idempotent no-op case. It also discloses the authorization requirements (actions.write, Agent Picks, and project management rights for the OAuth member or API-key creator), which annotations cannot express.

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-loads the destructive action in the first sentence, then layers preservation, parameter behavior, edge cases, and permissions. Six sentences are dense but each carries a distinct fact; the parameter sentence partially duplicates the schema, which is the only waste.

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?

For a destructive, no-output-schema mutation, the description covers what is destroyed, what is preserved, when the parameter is required, error modes, idempotency, and authorization. Nothing an agent needs to invoke this safely appears to be missing.

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 the single `setup` parameter is already fully documented, including the agent_picks_setup_required / agent_picks_setup_not_found error codes and the details.setups payload. The description restates the optional-unless-multiple condition without adding format or sourcing detail beyond the schema, 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 and resource ('Remove one of the project's Agent Picks setups') and immediately delimits it against sibling operations by describing what survives (tests and results stay readable) versus what is destroyed. An agent can distinguish this from devtune_save_agent_picks_setup and devtune_update_agent_picks_settings without opening either 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?

Gives concrete conditional guidance: pass `setup` when the project has several, omission is refused as agent_picks_setup_required, already-removed setups are a no-op, and removing the last setup leaves the project with none. It stops short of naming the alternative tool to use instead when removal is the wrong operation, so it is clear context rather than full when/when-not/alternatives 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?