Skip to main content
Glama

ADS Beast

task_suggest

Scans clients for unanswered critical alerts, KPI goals at risk, campaigns without metrics and projected overspend, and creates tasks for the team. dry_run=true only lists what it found.

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": "task_suggest"
  }
}

Input Schema

NameRequiredDescriptionDefault
dry_runNotrue only validates; nothing is written.
client_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and openWorldHint=true. The description adds meaningful context beyond that by stating that it creates tasks for the team (a real mutation) and that dry_run=true only lists findings without writing, giving the agent a safe preview semantics. It doesn't discuss permissions or what happens on re-runs, but the mutation and preview behavior are well disclosed.

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 tightly written sentences with no filler. The core action is front-loaded, and the dry_run caveat follows immediately after.

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

Completeness4/5

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

For a moderate-complexity mutation tool with no output schema, the description covers what it scans, what it produces, and the preview mode. The main gap is the undefined client_id scope, but overall it gives enough to call the tool 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?

Schema coverage is 50%: dry_run is documented in the schema and reinforced by the description's preview semantics. client_id has no description anywhere, and the description says 'Scans clients' (plural) without clarifying whether client_id narrows the scan to a single client. With only half the parameters covered, the description does not fully compensate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb (Scans) plus the concrete trigger sources (unanswered critical alerts, KPI goals at risk, campaigns without metrics, projected overspend) and the resulting action (creates tasks for the team). This clearly distinguishes it from a generic manual task creator, though it doesn't name task_create explicitly as the alternative.

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

Usage Guidelines3/5

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

It implies when to use it by listing the problem categories it scans, and it explains the dry_run path for a preview-only run. However, there is no explicit guidance on when NOT to use it versus task_create, or on prerequisites such as needing alert/KPI data to already exist.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.