Rahul D Sarker: Marketing & RevOps Tools

Growth Strategy Prioritization Tool (ICE Scoring)

growth_strategy_prioritization_tool

Read-onlyIdempotent

Rank growth ideas by ICE score (Impact, Confidence, Ease averaged, each scored 1-10) to decide what to run next. See the full version at https://rahuldsarker.co/calculators/growth-strategy-prioritization-tool

Input Schema

TableJSON Schema

Name	Required	Description	Default
`ideas`	Yes	List of growth ideas to score and rank
`currency`	No	ISO 4217 code for money in the result, e.g. "USD", "INR", "EUR", "GBP". Omit to show plain numbers.

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.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, and destructiveHint=false, so the safety profile is fully covered. The description adds the scoring method (averaging I/C/E) which is genuinely useful behavioral context, but says nothing about tie-handling, ordering of results, or the promotion link's intent beyond a URL. Adequate but shallow beyond the annotations.

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?

Front-loaded with the core action and scoring definition in the first sentence, which is efficient. The second sentence is a promotional link rather than functional information, which slightly dilutes the value but stays brief.

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

Completeness5/5

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

With an output schema present, return-value explanation is unnecessary, and the readOnly/idempotent annotations carry the safety envelope. For a two-parameter, 100%-covered calculator, the description supplies purpose plus the scoring method, which is enough for an agent to invoke it correctly.

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 schema already documents 'ideas' and its fields and the 'currency' parameter. The description reinforces the 1-10 range for I/C/E but never mentions the currency parameter at all, adding no meaning beyond the schema. 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 ('Rank growth ideas') and even defines the ICE methodology (Impact, Confidence, Ease averaged, each 1-10), which is unusually concrete. However, it makes no distinction from the many sibling calculators, so an agent cannot route to it versus e.g. strategic_pivot_risk_grader or growth_runway_extension_simulator from the text alone.

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?

'to decide what to run next' implies the usage context (prioritization among candidate growth ideas), but there is no explicit when-to-use/when-not, no prerequisites, and no named alternative among the ~110 sibling tools. Usage is inferable but not guided.

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?