Skip to main content
Glama

Rahul D Sarker: Marketing & RevOps Tools

No-Show Rate Revenue Restorer

no_show_rate_revenue_restorer
Read-onlyIdempotent

Calculate the revenue lost each month to demo no-shows, and how much would be recovered by cutting the no-show rate by 5 or 10 points. See the full version at https://rahuldsarker.co/calculators/no-show-rate-revenue-restorer

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": {
      "demosBookedPerMonth": "<demosBookedPerMonth>",
      "noShowRatePct": "<noShowRatePct>",
      "heldDemoCloseRatePct": "<heldDemoCloseRatePct>",
      "avgDealValue": "<avgDealValue>"
    },
    "name": "no_show_rate_revenue_restorer"
  }
}

Input Schema

NameRequiredDescriptionDefault
currencyNoISO 4217 code for money in the result, e.g. "USD", "INR", "EUR", "GBP". Omit to show plain numbers.
avgDealValueYesAverage deal value
noShowRatePctYesCurrent no-show rate, as a percentage
demosBookedPerMonthYesDemos booked per month
heldDemoCloseRatePctYesClose rate for held demos, as a percentage

Output Schema

NameRequiredDescriptionDefault
urlYes
kindYes
toolYesThe calculator tool that produced this result
notesYes
titleYes
inputsYes
compactYes
metricsYesEvery "Label: value" line of the result; value is the first number on the line
currencyYes
benchmarksYesRule-of-thumb verdicts for the headline numbers
bookingUrlYes
calculatorYesSlug of the interactive calculator on rahuldsarker.co

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • 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"
      +}
  2. First observed

TDQS

A4/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 the safety profile is covered. The description adds the calculation's scenario focus but does not disclose assumptions, currency handling, or other behavioral details beyond what the schema and annotations provide.

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?

The first sentence is front-loaded and directly states what the tool calculates. The second sentence is a promotional link, which is not essential for tool invocation, but overall the description remains short and readable.

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?

The tool is a deterministic calculator with full schema coverage, rich annotations, and an output schema. The description sufficiently explains the calculation scope and recovered-rate scenarios, so an agent has what it needs to invoke the tool 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 all five parameters are already documented in the input schema. The description does not add parameter-level meaning beyond the high-level calculation purpose, making the baseline of 3 appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource: calculating monthly revenue lost to demo no-shows and recovery from reducing the no-show rate by 5 or 10 points. This is granular enough to distinguish it from the many generic marketing and revenue calculators in the sibling list.

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

Usage Guidelines4/5

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

It gives a clear usage context—analyzing demo no-show revenue loss and scenario-based recovery—but does not explicitly say when to avoid it or name alternative tools. The context is sufficient for an agent to know when this calculator applies.

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.

Resources