Skip to main content
Glama

Advertising Adstock Decay

bpj_advertising_adstock_decay
Read-onlyIdempotent

Decay opening adstock by the supplied half-life and add a new exposure pulse at period end.

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": {
      "carry": "<carry>",
      "halfLife": "<halfLife>",
      "days": "<days>",
      "pulse": "<pulse>"
    },
    "name": "bpj_advertising_adstock_decay"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysYes
carryYes
pulseYes
halfLifeYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.7/5.0
Behavior2/5

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

The annotations already declare the operation as read-only, idempotent, and non-destructive, so the safety profile is covered. The description adds only a high-level transformation statement and does not disclose the exact decay formula, output format, edge-case behavior for days or halfLife, or how the pulse is combined with the decayed carry. For a computational tool, this leaves meaningful behavioral gaps.

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 definition is a single front-loaded sentence with no wasted wording. It is compact and readable. Its brevity contributes to the missing formula and return semantics, but the sentence itself is structurally efficient.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

This is a four-parameter computational tool with no output schema and no schema descriptions. The description does not state the exact formula, the return value, or edge-case semantics, which an agent would need in order to interpret results correctly. The annotations cover safety, but the computational contract is incomplete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate for the four undocumented numeric parameters. It loosely names the concepts of opening adstock, half-life, and new exposure pulse, but it does not clarify the role of 'days' or give the formula relating halfLife and days to the decayed result. It adds little meaning beyond the schema titles.

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 states a specific operation: decay an existing adstock amount by a half-life and add a new exposure pulse at period end. It is clear enough to distinguish this as an advertising adstock calculation from unrelated sibling tools. It does not explicitly differentiate from any closely related alternative, but no direct alternative is apparent in the supplied context.

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 provides no explicit when-to-use guidance, prerequisites, or conditions for choosing this tool over alternatives. Usage is only implied by the adstock terminology. There are no exclusions or contextual examples.

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.