Skip to main content
Glama

SpendCanary free Google Ads tools

ROAS calculator

roas
Read-onlyIdempotent

Return on ad spend from sales and ad spend, plus the break-even ROAS and profit for a profit margin.

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": {
      "revenue": "<revenue>",
      "ad_spend": "<ad_spend>"
    },
    "name": "roas"
  }
}

Input Schema

NameRequiredDescriptionDefault
revenueYesSales from the ads (conversion value) in the period.
ad_spendYesWhat the ads cost in the same period.
currencyNoCurrency code for the amounts; amounts are shown in it, never converted.USD
margin_percentNoProfit margin in percent, for the break-even ROAS.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered by structured data. The description adds that three values come back (ROAS, break-even ROAS, profit), which is useful given there is no output schema, but says nothing about units, rounding, or error behavior on zero ad spend.

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 sentence with no filler, and the primary output is front-loaded. The wording is slightly compressed ('from sales and ad spend, plus ... for a profit margin') but remains readable and efficiently sized for a simple calculator.

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 pure deterministic calculator with full schema coverage and complete annotations, the description covers the key unknown: what is returned (ROAS, break-even ROAS, profit). Edge cases such as zero ad spend are unaddressed, but the essentials for correct invocation are present.

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 every parameter (including the currency enum's 'never converted' semantics and the margin_percent 0-100 range) is already documented in the schema. The description only restates that margin feeds the break-even calculation, adding little beyond the schema.

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?

'Return on ad spend from sales and ad spend, plus the break-even ROAS and profit' names the specific metric computed and the inputs it is derived from, so an agent can tell it apart from siblings like cpc or daily_budget_max_spend on substance. It stops short of explicitly differentiating itself from any named 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?

Usage is implied rather than stated: the phrasing makes clear this is a computation from revenue and ad spend, and that margin_percent is only needed for the break-even figure. There is no explicit when-to-use/when-not guidance and no alternatives are pointed to.

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.