Skip to main content
Glama

Rahul D Sarker: Marketing & RevOps Tools

Advertising to Sales Ratio Calculator

advertising_to_sales_ratio_calculator
Read-onlyIdempotent

Calculate the advertising-to-sales (A/S) ratio from advertising spend and net sales, with an optional prior period for the trend and the incremental ratio. See the full version at https://rahuldsarker.co/calculators/advertising-to-sales-ratio-calculator

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": {
      "adSpend": "<adSpend>",
      "netSales": "<netSales>"
    },
    "name": "advertising_to_sales_ratio_calculator"
  }
}

Input Schema

NameRequiredDescriptionDefault
adSpendYesAdvertising spend for the latest period
currencyNoISO 4217 code for money in the result, e.g. "USD", "INR", "EUR", "GBP". Omit to show plain numbers.
netSalesYesNet sales for the same period (after returns, discounts and taxes)
priorAdSpendNoOptional: advertising spend for the prior period
priorNetSalesNoOptional: net sales for the prior period

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. Added

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds that supplying a prior period yields a trend and an incremental ratio, which is useful behavioral detail, but nothing about error handling or result shape.

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, purpose front-loaded, no filler. The trailing promotional URL does not help tool selection but is brief enough not to materially hurt the structure.

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?

An output schema exists so return values need not be explained, and the full parameter set is covered by the schema. For a stateless calculator the definition is essentially complete, missing only routing context against sibling calculators.

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, including the currency format and the net-sales definition. The description restates adSpend/netSales/prior period but adds no syntax or edge-case meaning beyond the schema, so the baseline of 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 (Calculate) and resource (advertising-to-sales ratio), plus the two required inputs and the optional prior-period extension. An agent knows exactly what this computes, though it never names a sibling (e.g. roas_calculator) to distinguish the many adjacent calculators.

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?

There is no when-to-use or when-not-to-use guidance and no named alternative. With dozens of sibling ratio/ROI calculators, the description leaves the agent to infer that this is the right one for A/S ratio from the name alone.

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