Skip to main content
Glama

Conversion Funnel Backsolve

bpj_funnel_backsolve
Read-onlyIdempotent

Backsolve the minimum estimated volume at each stage for a target conversion count.

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": {
      "target": "<target>",
      "rates": "<rates>"
    },
    "name": "bpj_funnel_backsolve"
  }
}

Input Schema

NameRequiredDescriptionDefault
ratesYes
targetYes

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?

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and a closed-world scope, so the safety profile is fully covered. Beyond that, the description adds nothing: it does not say how the result is ordered, how rounding is handled, or what happens when rates imply impossible volumes (e.g. a 0% stage).

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 no filler, and the object being solved for is stated early. Its brevity is efficient rather than padded, though the terseness leaves semantic gaps covered elsewhere in the scores.

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, the description is the only place return semantics could be explained, yet it does not state that the result is a per-stage list, its ordering, or its shape. For a numeric computation tool where the input encoding (a multi-line percentage string) is non-obvious, this leaves too much unspecified.

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% (only titles are present), so the description carries the burden and does not meet it. It never mentions the 'rates' string format conventions, the max-8 stage limit, the one-percentage-per-line encoding, or how the ordering of rates maps to the returned stages.

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 ('backsolve') and a specific output ('minimum estimated volume at each stage') driven by a target conversion count, so the agent can tell it is the inverse-of-a-funnel calculation rather than a forward projection. It stops short of naming or contrasting any sibling such as bpj_conversion_confidence or bpj_break_even_units, so differentiation is left to inference.

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 guidance, no when-not-to-use, and no pointer to an alternative tool. The agent must infer from the title alone that this is the right choice when it has a target count and stage rates rather than observed funnel data.

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.