Skip to main content
Glama

Channel Mix Contribution

bpj_channel_mix_contribution
Read-onlyIdempotent

Combine direct and marketplace order counts and per-order contribution to show channel totals and blended unit economics.

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": {
      "direct": "<direct>",
      "meanDirect": "<meanDirect>",
      "market": "<market>",
      "meanMarket": "<meanMarket>"
    },
    "name": "bpj_channel_mix_contribution"
  }
}

Input Schema

NameRequiredDescriptionDefault
directYes
marketYes
meanDirectYes
meanMarketYes

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 readOnlyHint, idempotentHint, non-destructive, and closed-world, so the safety profile is fully covered and the description correctly does not contradict it. The description adds that the operation is a combination yielding totals and a blend, but says nothing about how the blend is computed, whether rounding occurs, or what the return looks like (no output schema exists).

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 that states inputs and output with no filler. Nothing redundant and no restating of the name.

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 four-required-parameter pure calculation, the description covers the conceptual inputs and names the outputs, and annotations handle safety. But with no output schema, the vague phrase 'channel totals and blended unit economics' is the only return-value information, and the blending formula and unit conventions are left unspecified.

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 carries the parameter burden. It does semantically map all four inputs ('order counts' for direct/market and 'per-order contribution' for each), which is more than the bare titles offer. However, it leaves units/currency ambiguous and never explains that meanDirect/meanMarket may be negative or how counts and means combine, so it only partially compensates.

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 operation ('combine') and its inputs ('direct and marketplace order counts and per-order contribution') plus the output concept ('channel totals and blended unit economics'). An agent can tell this is a deterministic aggregation/calculator tool. It doesn't explicitly contrast with a sibling, which keeps it at 4 rather than 5.

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 described inputs make clear it is called when you have both channel order counts and per-order contribution figures. There is no explicit when-to-use, when-not-to-use, or named alternative among the many bpj_* calculators, so an agent must infer fit from the input shape.

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.