Rahul D Sarker: Marketing & RevOps Tools

Micro-Budget Ad Feasibility Checker

micro_budget_ad_feasibility_checker

Read-onlyIdempotent

Check whether a small daily ad budget can generate the ~50 weekly conversions platforms typically need to exit the learning phase. See the full version at https://rahuldsarker.co/calculators/micro-budget-ad-feasibility-checker

Input Schema

TableJSON Schema

Name	Required	Description
`estCpa`	Yes	Estimated CPA (cost per optimization event)
`currency`	No	ISO 4217 code for money in the result, e.g. "USD", "INR", "EUR", "GBP". Omit to show plain numbers.
`dailyBudget`	Yes	Daily ad budget

Output Schema

TableJSON Schema

Name	Required	Description
`url`	Yes
`kind`	Yes
`tool`	Yes	The calculator tool that produced this result
`notes`	Yes
`title`	Yes
`inputs`	Yes
`compact`	Yes
`metrics`	Yes	Every "Label: value" line of the result; value is the first number on the line
`currency`	Yes
`benchmarks`	Yes	Rule-of-thumb verdicts for the headline numbers
`bookingUrl`	Yes
`calculator`	Yes	Slug of the interactive calculator on rahuldsarker.co

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedSep 30, 2026

addedInput schema / properties / currency

Added value: +{
+  "description": "ISO 4217 code for money in the result, e.g. \"USD\", \"INR\", \"EUR\", \"GBP\". Omit to show plain numbers.",
+  "pattern": "^[A-Za-z]{3}$",
+  "type": "string"
+}

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "additionalProperties": false,
+  "properties": {
+    "benchmarks": {
+      "description": "Rule-of-thumb verdicts for the headline numbers",
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "band": {
+            "type": "string"
+          },
+          "display": {
+            "type": "string"
+          },
+          "metric": {
+            "type": "string"
+          },
+          "name": {
+            "type": "string"
+          },
+          "read": {
+            "type": "string"
+          },
+          "segment": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "source": {
+            "type": "string"
+          },
+          "target": {
+            "type": "string"
+          },
+          "tone": {
+            "enum": [
+              "good",
+              "ok",
+              "warn",
+              "bad"
+            ],
+            "type": "string"
+          },
+          "value": {
+            "type": "number"
+          }
+        },
+        "required": [
+          "metric",
+          "name",
+          "value",
+          "display",
+          "band",
+          "tone",
+          "read",
+          "target",
+          "segment",
+          "source"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "bookingUrl": {
+      "type": "string"
+    },
+    "calculator": {
+      "description": "Slug of the interactive calculator on rahuldsarker.co",
+      "type": "string"
+    },
+    "compact": {
+      "type": "boolean"
+    },
+    "currency": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "inputs": {
+      "additionalProperties": {},
+      "propertyNames": {
+        "type": "string"
+      },
+      "type": "object"
+    },
+    "kind": {
+      "const": "calculator",
+      "type": "string"
+    },
+    "metrics": {
+      "description": "Every \"Label: value\" line of the result; value is the first number on the line",
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "display": {
+            "type": "string"
+          },
+          "label": {
+            "type": "string"
+          },
+          "unit": {
+            "anyOf": [
+              {
+                "enum": [
+                  "currency",
+                  "x",
+                  "%",
+                  "months"
+                ],
+                "type": "string"
+              },
+              {
+                "type": "null"
+              }
+            ]
+          },
+          "value": {
+            "type": [
+              "number",
+              "null"
+            ]
+          }
+        },
+        "required": [
+          "label",
+          "value",
+          "unit",
+          "display"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "notes": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "title": {
+      "type": "string"
+    },
+    "tool": {
+      "description": "The calculator tool that produced this result",
+      "type": "string"
+    },
+    "url": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "kind",
+    "tool",
+    "title",
+    "calculator",
+    "url",
+    "bookingUrl",
+    "currency",
+    "compact",
+    "inputs",
+    "metrics",
+    "notes",
+    "benchmarks"
+  ],
+  "type": "object"
+}

First observedSep 29, 2026

TDQS

A3.5/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety and determinism are covered structurally. The description adds genuinely useful domain behavior — the ~50 weekly conversions learning-phase threshold — which is not derivable from the schema or annotations, though it says nothing about how the verdict is computed or what the returned result contains beyond what the output schema supplies.

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, front-loaded with the actual check and its threshold; nothing is buried. The trailing promotional URL is not useful to an agent deciding how to invoke the tool, which slightly dilutes an otherwise tight definition.

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 a 3-parameter schema at full description coverage, read-only annotations, and a declared output schema, the description only needs to convey the domain intent and success criterion, which it does. An agent can call it correctly; only the absence of alternatives/disambiguation keeps it from being fully complete.

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 dailyBudget, estCpa and currency are already fully documented in the schema, including the ISO 4217 pattern and the 'omit for plain numbers' behavior. The description adds no parameter-level syntax or format detail beyond that, so the baseline 3 applies.

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?

States a specific verb and resource: checks whether a small daily ad budget yields the ~50 weekly conversions needed to exit a platform's learning phase. That is concrete and distinct from generic CPA or spend calculators in the sibling list, though it does not name which sibling (e.g. cpl_cpa_calculator, ad_spend_waste_calculator) it should be preferred over.

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?

The phrase 'small daily ad budget' implies the scenario in which this applies (early-stage / low-budget campaigns stuck in learning phase), but there is no explicit when-not guidance or named alternative for a larger-budget feasibility question. Usage context is inferable rather than stated.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Rahul D Sarker: Marketing & RevOps Tools tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?