Skip to main content
Glama

List Spillmark's free calculators

list_calculators
Read-only

Spillmark's free Amazon and Meta ads calculators (holdout test size, brand-size MDE, geo holdout states, ad waste, Meta ROAS reality check, incremental ROAS, break-even ROAS, ACoS, TACoS, Amazon fees and profit, LTV and CAC), with each one's inputs and example values. Use run_calculator to run one.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_calculators"
  }
}

Input Schema

NameRequiredDescriptionDefault
qNoFilter by words in the name or summary, e.g. 'holdout' or 'fees'

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds useful return-content context — each entry carries inputs and example values — which matters since there is no output schema. It does not describe ordering or pagination, so a 4 rather than 5.

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 resource and a routing instruction in the second sentence; every element serves discovery. The long parenthetical calculator list is dense but genuinely informative, not filler.

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?

A read-only, one-optional-param listing tool with no output schema, and the description compensates by stating what each result entry contains (inputs and example values). An agent has enough to call it correctly and know what comes back.

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 coverage is 100% with a clear description and example values for the single optional 'q' filter, so the schema carries the burden. The description never mentions filtering, contributing nothing beyond the schema — baseline 3.

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?

States a specific verb and resource ('list ... calculators') and enumerates the concrete calculator set covered, so an agent knows exactly what is being listed without opening a schema. It is clearly distinct from the sibling run_calculator, which executes one.

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?

Explicitly routes the agent: 'Use run_calculator to run one,' establishing the discover-then-execute sequence. It stops short of saying when not to use this tool (e.g., when the calculator name is already known), so not a full 5.

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.