Rahul D Sarker: Marketing & RevOps Tools

CRM Cleanup ROI Calculator

crm_cleanup_roi_calculator

Read-onlyIdempotent

Quantify the rep hours and revenue lost to dirty CRM data each year, and the selling capacity a cleanup would free up. See the full version at https://rahuldsarker.co/calculators/crm-cleanup-roi-calculator

Input Schema

Name	Required	Description
`reps`	Yes	Reps/users on the CRM
`currency`	No	ISO 4217 code for money in the result, e.g. "USD", "INR", "EUR", "GBP". Omit to show plain numbers.
`hourlyCost`	Yes	Fully-loaded hourly cost per rep
`hoursWastedPerWeek`	Yes	Hours per week lost to bad data, per rep

Output 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

B3.2/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 and the description does not contradict it. The description confirms the output is an annualized loss/capacity figure, but adds nothing about determinism, units of the result, or how the currency omission behaves.

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 short sentences, front-loaded with the outcome the agent cares about. The trailer pointing at an external full version is a slight dilution but does not obscure the core statement.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists and annotations cover safety, so returns and side effects need no elaboration. What is missing is the one thing the structured fields cannot supply: how this differs from the sibling crm_roi_calculator, leaving selection ambiguous.

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 reps, hoursWastedPerWeek, hourlyCost and currency are all documented in the schema itself. The phrase 'each year' mildly clarifies that the weekly input is annualized, but that is marginal added meaning, 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?

Specific verb (quantify) plus specific outputs (rep hours and revenue lost to dirty CRM data, selling capacity freed by cleanup), which is far more than a restatement of the name. It does not distinguish itself from the nearby sibling crm_roi_calculator, so an agent must infer which CRM-ROI tool applies.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description never states when to reach for this tool instead of crm_roi_calculator, data_enrichment_value_predictor, or the other ROI calculators in the catalog. The only secondary content is an external link to a 'full version', which is not usage guidance.

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?