Skip to main content
Glama

Position-Based Attribution Credit

bpj_position_based_attribution_credit
Read-onlyIdempotent

Allocate conversion value to first and last touches and spread residual credit evenly over middle touches; a two-touch path must use all credit at its ends.

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": {
      "touches": "<touches>",
      "first": "<first>",
      "last": "<last>",
      "value": "<value>"
    },
    "name": "bpj_position_based_attribution_credit"
  }
}

Input Schema

NameRequiredDescriptionDefault
lastYes
firstYes
valueYes
touchesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior4/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 description is free to spend its words on the allocation algorithm itself — fixed ends plus evenly spread residual — which is genuine behavioral information. What it omits is edge behavior when first + last exceeds 100 or when residual would be negative.

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 front-loaded sentence with the core allocation rule first and the edge case after a semicolon; no filler. It is dense but readable, and only the missing output/validation detail keeps it from being ideal.

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 pure calculation tool with no output schema, the definition covers the algorithm but not the return shape (a per-touch allocation list? totals?) or input validation. Combined with 0% schema coverage, an agent still has to guess at edge cases before calling it.

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 must carry parameter meaning; it does explain that `first` and `last` are endpoint credit shares and that `touches` counts a converting path with a minimum of two. However it never clarifies the unit relationship (percentages summing to what), the validation rule implied for two-touch paths, or how `value` is apportioned in the return.

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?

States a specific verb (allocate) and resource (conversion value / attribution credit) and pins down the algorithm: first and last touches get fixed credit, residual spread evenly over middle touches. It is unambiguous what the tool computes, though it does no explicit sibling differentiation.

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 when-to-use or when-not-to-use guidance and no alternatives named (e.g., even-spread or time-decay attribution). The two-touch rule is an internal correctness constraint, not usage guidance, so an agent learns nothing about when to choose this model.

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.