Skip to main content
Glama

Ad Spec Guard

check_decision_readiness

Read-only

Decide whether a live campaign has produced enough data to justify pausing it, scaling its budget, rotating a creative or switching bidding strategy, and whether it is still inside the platform's learning phase. Returns the unmet requirements with the shortfall and an estimate of how long to wait. Call it before recommending any change and before calling a metric good or bad. For a verdict on a cost per acquisition or return on ad spend use 'judge_metric'; for a verdict on a click-through rate or conversion rate use 'judge_rate_metric', which is gated on clicks rather than conversions.

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": {
      "platform": "<platform>",
      "decision": "<decision>"
    },
    "name": "check_decision_readiness"
  }
}

Input Schema

NameRequiredDescriptionDefault
spendNoAmount spent so far, in USD.
clicksNoClicks recorded so far.
decisionYesThe decision being considered.
platformYesAd platform. Known keys: google, google_display, google_search, linkedin, meta, microsoft, tiktok.
conversionsNoConversions recorded so far. Omit it if it was not measured; do not pass 0 for unknown, because zero conversions after real traffic is a finding.
impressionsNoImpressions recorded so far.
days_runningNoDays the campaign has been delivering.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare this is a read-only, non-destructive, closed-world check, so the safety profile is covered. The description adds real behavioral context beyond that: it returns unmet requirements with the shortfall and an estimated wait time, and it notes the learning-phase check. It doesn't discuss edge cases like missing spend or impression data, keeping it just short of a 5.

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?

The purpose and the routing constraints are front-loaded, and every sentence carries information. It is slightly dense with the sibling routing detail, but no sentence is filler.

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, but the description explains what the tool returns — unmet requirements, shortfalls, and a wait-time estimate — which is the key return behavior an agent needs. Combined with a fully described 7-parameter schema, an agent has everything needed to call it correctly and interpret the result.

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 schema already documents every parameter, including the important 'omit conversions if unmeasured, do not pass 0' nuance. The description adds a little meaning by tying the decision enum values to sibling tools and clarifying the clicks-vs-conversions gating, but most parameter semantics live in 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?

The description opens with a specific verb and resource — deciding whether a live campaign has enough data to justify pausing, scaling, rotating creative, or switching bid strategy — and enumerates the decision types it covers. It explicitly differentiates itself from 'judge_metric' (CPA/ROAS) and 'judge_rate_metric' (CTR/CVR), so an agent can distinguish it from 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?

It gives explicit when-to-use guidance: 'Call it before recommending any change and before calling a metric good or bad.' It also names the alternatives and the condition that selects them — judge_metric for cost/return metrics, judge_rate_metric for rate metrics, gated on clicks rather than conversions — leaving nothing to inference.

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.