Skip to main content
Glama

Campaign Budget Pacing

bpj_campaign_budget_pacing
Read-onlyIdempotent

Compare spend to a uniform calendar pacing line and calculate the allowable daily spend over remaining days.

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>",
      "spend": "<spend>",
      "totalDays": "<totalDays>",
      "elapsed": "<elapsed>"
    },
    "name": "bpj_campaign_budget_pacing"
  }
}

Input Schema

NameRequiredDescriptionDefault
spendYes
budgetYes
elapsedYes
totalDaysYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered without the description. The description adds that the operation is a deterministic comparison producing a derived daily allowance, but it does not disclose edge-case behavior such as elapsed exceeding totalDays or zero remaining days, which matters for a pure calculation tool.

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?

A single well-formed sentence with the comparison front-loaded and the computed output second; nothing is redundant. It is slightly dense with undefined terminology, but no sentence is wasted.

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?

With no output schema and four required parameters, the description is the only place to explain the return shape (variance vs. pacing line, the daily allowance value, any status flag) and it does not. For a calculator-style tool whose whole value is the returned numbers, the definition leaves the agent guessing at what it will receive.

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%, but each property carries a descriptive title ("Spend to date", "Media budget", "Completed campaign days", "Campaign calendar days") plus bounds, which carries much of the semantic load. The description reinforces the budget/spend pairing and the "remaining days" derivation but never explicitly ties it to the elapsed/totalDays relationship, so it adds only marginal meaning.

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 uses specific verbs ("Compare spend", "calculate") against a named resource concept ("uniform calendar pacing line") and states the produced quantity ("allowable daily spend over remaining days"). An agent can tell this is a pacing/variance computation rather than a formatting or lookup utility, though the term "uniform calendar pacing line" is jargon that isn't defined.

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 explicit when-to-use or when-not-to-use guidance, and no alternative is named. The campaign-budget framing implies the context, but the agent gets no statement about prerequisites (e.g., that spend and budget must be in the same currency/unit) or what to do if pacing is already off-track.

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.