Skip to main content
Glama

SpendCanary free Google Ads tools

CPC calculator

cpc
Read-onlyIdempotent

Cost per click from spend and clicks, or clicks from spend and cost per click (any two of the three), plus CPM and click-through rate from impressions.

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

Input Schema

NameRequiredDescriptionDefault
spendNoAd spend.
clicksNoClicks.
currencyNoCurrency code for the amounts; amounts are shown in it, never converted.USD
impressionsNoImpressions, for CPM and click-through rate.
cost_per_clickNoCost per click; give two of spend, clicks and cost_per_click.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/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 a closed world, so the safety profile is covered. The description adds the useful behavioral fact that results are computed outputs contingent on which inputs are supplied, but says nothing about what happens when fewer than two of the three inputs are given or how conflicting inputs are resolved.

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?

A single front-loaded sentence that covers the three outputs and the input constraint with no filler. Nothing is redundant with the tool name and each clause carries distinct information.

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?

With no output schema, the description does the job of naming what comes back (CPC, clicks, CPM, CTR) and what drives each. For a five-parameter, zero-required, side-effect-free calculator this is nearly sufficient; the only gap is the behavior when the input combination is insufficient.

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 baseline is 3; each parameter is already documented including the currency non-conversion rule. The description restates the two-of-three constraint that also appears in the cost_per_click schema description and adds no new semantics such as precedence when all three are supplied.

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 the derived metric (cost per click) and the exact input pairings that produce it, plus the secondary outputs CPM and click-through rate. An agent can tell this is a pure derivation tool rather than a data-fetch tool. It stops short of naming or contrasting any sibling (e.g. roas), so it does not fully differentiate.

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: 'any two of the three' tells the caller how to combine spend, clicks and cost_per_click, and 'from impressions' signals when CPM/CTR are available. There is no explicit statement of when to pick this tool over alternatives, nor any exclusion or precondition for missing inputs.

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.