Skip to main content
Glama

Stage-Weighted Sales Pipeline

bpj_weighted_sales_pipeline
Read-onlyIdempotent

Weight opportunity value in two disjoint pipeline stages by their close probabilities and compare expected bookings with target.

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": {
      "early": "<early>",
      "earlyWin": "<earlyWin>",
      "late": "<late>",
      "lateWin": "<lateWin>",
      "target": "<target>"
    },
    "name": "bpj_weighted_sales_pipeline"
  }
}

Input Schema

NameRequiredDescriptionDefault
lateYes
earlyYes
targetYes
lateWinYes
earlyWinYes

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=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety and determinism profile is fully covered elsewhere. The description adds the useful constraint that the two stages are disjoint (no overlap/double counting) and that the result is a comparison against target, but it does not say what the response contains or how ties/zero probabilities behave. No contradiction with annotations.

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 tightly packed sentence with no filler, front-loading the operation before the comparison. Nothing is redundant and nothing could be removed without losing meaning.

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 with no output schema, the description should at minimum indicate the form of the result (weighted total vs. variance to target, and whether probabilities are percentages). It gestures at the comparison but leaves the return shape and the exact formula implicit, which is a meaningful gap for a five-parameter numeric tool.

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 the semantic load. It does map the conceptual roles - early and late opportunity value, their respective close probabilities, and a booking target - which aligns with the five required parameters. But it never states the arithmetic (value x probability, summed, then differenced against target), nor that probabilities are on a 0-100 percent scale; that unit only appears in the schema's property titles, not the description.

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 and resource: weight opportunity value in two disjoint pipeline stages by close probability, then compare expected bookings against a target. That is concrete enough to distinguish it from the many other weighted-calculation siblings (weighted mean/median/variance, weighted capital cost, weighted coverage). It stops short of a fully explicit output statement, but the operation is identifiable.

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 by the arithmetic nature of the tool - an agent can infer it is a forecasting/scenario calculation rather than a lookup or mutation. However, there is no explicit when-to-use framing, no statement of prerequisites, and no mention of when a different sibling (e.g. a weighted-average or bridge tool) would be the better choice.

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.