DevTune MCP

devtune_cancel_agent_picks_test

DestructiveIdempotent

Cancel a queued or running paid Agent Picks test or re-test. Queued runs are cancelled at once and reserve nothing more; running runs keep their reservation until they settle, so a refund is not immediate: refunded_micros and released_at on devtune_get_agent_picks_test show when credits return. Returns status cancelled and test_id; a repeat returns the same. Starter tests cannot be cancelled (not_found). An ended test is refused as test_finished. Works while the account is paused. Requires actions.write and Agent Picks. The OAuth member, or the member who created the API key, needs project management rights.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "test_id": "<test_id>"
    },
    "name": "devtune_cancel_agent_picks_test"
  }
}

Input Schema

Name	Required	Description	Default
`test_id`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 25, 2026

TDQS

A4.6/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, and the description adds real depth beyond them: the differing refund timing for queued vs running runs, where refunded_micros/released_at surface, idempotent repeat behavior ('a repeat returns the same'), and the required scopes/permissions. This is behavior an agent could not infer from the schema or annotations.

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 purpose and the key cancellation/refund distinction; every sentence carries information (refund timing, idempotency, error cases, permissions). It is dense but not padded, though a few clauses about permissions could be tightened.

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?

No output schema exists, yet the description documents the return payload ('status cancelled and test_id'), the refund-signal fields, and error outcomes, and it covers auth requirements. An agent has everything needed to invoke and interpret results correctly.

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?

Only one parameter (test_id, uuid) with 0% schema description coverage. The description only references test_id as a returned field, not as an input, so it adds no semantics about which identifier to supply. With a single trivial parameter the gap is minor, but the description does not compensate for the missing schema documentation.

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?

Opens with a specific verb and resource: 'Cancel a queued or running paid Agent Picks test or re-test.' The scope qualifiers (queued vs running, paid, test vs re-test) let an agent distinguish this from devtune_start_agent_picks_starter_test, devtune_get_agent_picks_test, and the draft/quote siblings without opening schemas.

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?

Explicitly states which cases this applies to (queued or running, works while account paused) and which do not: 'Starter tests cannot be cancelled (not_found)' and 'An ended test is refused as test_finished.' An agent knows before calling whether the target is eligible and what error to expect otherwise.

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?