Skip to main content
Glama

Media Reach and Frequency Plan

bpj_media_reach_frequency_plan
Read-onlyIdempotent

Translate media budget and CPM to impressions and estimate unique reach at the supplied average frequency.

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": {
      "budget": "<budget>",
      "cpm": "<cpm>",
      "frequency": "<frequency>"
    },
    "name": "bpj_media_reach_frequency_plan"
  }
}

Input Schema

NameRequiredDescriptionDefault
cpmYes
budgetYes
frequencyYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.3/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 agent knows this is a safe, deterministic, closed computation. The description adds only that the reach figure is an 'estimate' at the supplied average frequency, which hints at approximation without explaining the underlying model; it says nothing about units, rounding, or what happens when frequency is 1.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence mapping inputs to outputs with no filler or restatement of the name. Every clause earns its place.

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?

For a three-parameter pure-function calculator with no output schema and no annotations gap, the description covers the core transformation. It omits the output shape (two numbers? a structured object?), unit conventions, and the assumptions behind the reach estimate, which an agent needs to interpret results 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 0% — only bare titles like 'Media budget' and 'Cost per thousand impressions' carry meaning. The description partially compensates by tying budget+CPM to impressions and clarifying that frequency is 'average impressions per reached person', but it does not state the currency/unit assumed for budget, the impression denominator (per 1000), or which parameters drive which output.

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?

The verb phrase 'Translate media budget and CPM to impressions and estimate unique reach' names both the inputs and the two outputs, which is specific rather than tautological. It stops short of 5 because 'estimate unique reach' leaves the reach model ambiguous (it is not simply impressions/frequency), and nothing distinguishes it from the similarly named sibling 'bpj_frequency_cap_budget_ceiling'.

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 states what the tool computes but never says when to call it, what preconditions apply (e.g., budget must be in the same currency as CPM), or which sibling to use for a frequency-cap or budget-ceiling analysis. Usage is only inferable from the required parameter list.

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.