Skip to main content
Glama

Ad Spec Guard

estimate_budget_feasibility

Read-only

Work out whether a monthly budget can reach a target cost per acquisition or return on ad spend, and whether it produces enough weekly conversions for automated delivery to leave the learning phase. Nothing is filled in from industry averages: for any input not supplied, it solves for the value the goal would require and labels it as a condition rather than a forecast.

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": {
      "monthly_budget": "<monthly_budget>"
    },
    "name": "estimate_budget_feasibility"
  }
}

Input Schema

NameRequiredDescriptionDefault
ad_setsNoHow many ad sets or campaigns the budget is split across.
currencyNoCurrency code for the amounts supplied.USD
target_cpaNoTarget cost per acquisition.
target_roasNoTarget return on ad spend, as a multiple such as 4 for 4x.
expected_cpcNoCost per click. Supply it only if measured or quoted.
expected_cvrNoConversion rate, as 0.03 or 3 for three percent. Supply it only if measured.
monthly_budgetYesPlanned monthly media budget.
avg_order_valueNoAverage order value, required with a return goal.

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 readOnly, non-destructive, closed-world behavior, so the description's job is to add substance — and it does. It discloses a non-obvious behavioral trait: missing inputs are back-solved and labeled as conditions rather than forecasts, and no industry averages are substituted. It does not describe the shape of the returned result, which keeps it from 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?

Two sentences, no filler, with the core capability front-loaded. The second sentence is dense and slightly convoluted in its phrasing about solving and labeling, but every clause carries information an agent needs.

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 an 8-parameter analytical tool with no output schema, the description conveys the method and the treatment of missing inputs, which is the critical unknown. It does not clarify what happens if both target_cpa and target_roas are supplied, or if neither goal is given while only monthly_budget is required — a minor but real gap.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3. The description earns above baseline by explaining what happens when optional inputs like expected_cpc or expected_cvr are omitted — the tool solves for the required value instead of defaulting. That is meaning the schema does not convey.

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 names a specific computation: whether a monthly budget can hit a target CPA or ROAS and generate enough weekly conversions to exit the learning phase. That is concrete and clearly distinct from the sibling validation/preflight tools. It stops short of explicitly naming a sibling it should not be confused with, which keeps it at 4 rather than 5.

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 implied by the framing ('work out whether a monthly budget can reach...'), so an agent can infer this is a planning/feasibility check rather than a validation step. However, there is no explicit when-to-use or when-not-to-use statement, and no routing guidance against the check_decision_readiness or ab_test_significance siblings.

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.