Skip to main content
Glama

SpendCanary free Google Ads tools

Daily budget overspend calculator

daily_budget_max_spend
Read-onlyIdempotent

The most Google Ads can charge in one day (2× the average daily budget) and in a month (30.4×) for a campaign daily budget.

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": {
      "daily_budget": "<daily_budget>"
    },
    "name": "daily_budget_max_spend"
  }
}

Input Schema

NameRequiredDescriptionDefault
currencyNoCurrency code for the amounts; amounts are shown in it, never converted.USD
daily_budgetYesAverage daily budget of one campaign.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

The annotations already declare a safe, idempotent, closed-world read, so the description's job is to add informational value — and it does, by disclosing the exact multipliers (2× daily, 30.4× monthly) that define the output. That formula disclosure is genuinely beyond what annotations or the schema provide; only the shape of the returned values goes unstated.

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?

A single front-loaded sentence that carries the full formula with no filler. The nested parentheticals ('in one day (2× ...) and in a month (30.4×)') make it slightly harder to parse on first read than a flat phrasing would.

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 two-parameter pure calculator with full schema coverage, complete annotations, and no output schema, the description covers what the tool computes and for what scope. It declines to spell out return values or currency behavior, but the schema already handles the currency nuance, so the gap is minor.

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 100%, so both daily_budget and currency are already documented, including the important 'amounts are shown in it, never converted' note. The description's 'one campaign' wording usefully confirms the budget is per-campaign rather than account-level, but adds no further syntax or unit guidance beyond the schema baseline.

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 states a specific computation on a specific resource: the maximum a Google Ads campaign can be charged per day (2× average daily budget) and per month (30.4×). It is clearly distinct from sibling metrics like cpc, roas, or wasted_spend_from_search_terms, which report actuals rather than caps, though it never explicitly names those alternatives.

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?

Usage is only implied: the phrase 'for a campaign daily budget' signals the input domain and the purpose of checking overspend ceilings, but there is no explicit when-to-use statement, no mention of when the monthly vs daily figure matters, and no exclusions.

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.