Skip to main content
Glama

Share of Voice Impression Gap

bpj_brand_impression_share_gap
Read-onlyIdempotent

Hold competitors’ impressions fixed and solve for the brand impressions required to reach a target share of category impressions.

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": {
      "own": "<own>",
      "other": "<other>",
      "desired": "<desired>"
    },
    "name": "bpj_brand_impression_share_gap"
  }
}

Input Schema

NameRequiredDescriptionDefault
ownYes
otherYes
desiredYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description's real contribution is the modeling assumption that competitor impressions are held constant, which is genuinely useful context. It does not disclose the return value (required impressions vs. the gap), rounding, or behavior at boundary inputs such as a zero denominator.

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, dense sentence with no filler, and the operative assumption is front-loaded ahead of the objective. It is efficient, though the compression is part of why the input roles stay under-explained.

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?

Three required numeric parameters, no output schema, and no nested structure make this a simple tool, but the description leaves the return semantics and the 'own' parameter's role unresolved, and gives no edge-case notes. With annotations covering safety, the remaining gaps are moderate rather than severe.

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%, so the description has to carry parameter meaning; it partially does by mapping 'other' to competitors' impressions and 'desired' to the target share. It never explains what role 'own' plays — whether it is the current baseline used to compute the required delta, or merely contextual — leaving a genuine ambiguity for one of three required numeric inputs.

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 computation: solve for the brand impressions needed to hit a target share of category impressions, holding competitors fixed. That is much more than a restatement of the title. It stops short of tying the result to the tool name's 'gap' framing (i.e., whether the output is required impressions or the difference from current own impressions).

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 implied rather than stated: the phrasing 'hold competitors' impressions fixed' signals a planning/what-if scenario and reveals the model's core assumption (no competitor response). There is no explicit when-to-use, when-not-to-use, or comparison to any alternative, and no prerequisites are given.

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.