Skip to main content
Glama

Frequency Cap Budget Ceiling

bpj_frequency_cap_budget_ceiling
Read-onlyIdempotent

Calculate the theoretical impression ceiling from audience size and per-person frequency cap and value it at the supplied CPM.

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": {
      "audience": "<audience>",
      "cap": "<cap>",
      "cpm": "<cpm>"
    },
    "name": "bpj_frequency_cap_budget_ceiling"
  }
}

Input Schema

NameRequiredDescriptionDefault
capYes
cpmYes
audienceYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, closed-world and non-destructive, so the safety profile is covered. The description usefully adds that the result is a 'theoretical' ceiling valued at a CPM, but it omits the computation shape (audience × cap, divided by 1000, times CPM) and any rounding or currency assumptions.

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 with the verb, the result, and the input mapping in order, with no filler. Nothing in it could be removed without losing meaning.

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, no-output-schema tool the description is adequate on inputs but silent on the return shape — whether it returns one figure (impressions) or two (impressions plus the CPM-valued budget), which the phrase 'and value it' leaves ambiguous. A brief statement of what comes back would close the gap.

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% and the only in-schema text is short titles, so the description must carry the meaning — and it does map all three parameters: audience size, per-person frequency cap, and CPM. However, it adds no units, currency, or period semantics beyond what the titles already hint at.

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 description names a specific verb ('Calculate') and a specific output ('theoretical impression ceiling'), plus the three inputs that produce it. It is distinguishable from siblings like bpj_media_reach_frequency_plan or bpj_geom_spherical_cap, though it never explicitly contrasts itself with them.

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?

Usage is only implied: the word 'theoretical' signals this is an upper-bound sizing/valuation calculation rather than a forecast or an actual delivery measurement. There is no explicit when-to-use, when-not-to-use, or named alternative among the many sibling ceiling/budget tools.

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.