Skip to main content
Glama

Weighted Shortest Job First

bpj_weighted_shortest_job
Read-onlyIdempotent

Combine relative value, urgency and risk or opportunity scores and divide by job size to compute WSJF.

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": {
      "business": "<business>",
      "urgency": "<urgency>",
      "opportunity": "<opportunity>",
      "size": "<size>"
    },
    "name": "bpj_weighted_shortest_job"
  }
}

Input Schema

NameRequiredDescriptionDefault
sizeYes
urgencyYes
businessYes
opportunityYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already establish read-only, idempotent, non-destructive behavior. The description adds the core formula and the fact that job size is the denominator, but it does not explain output format, rounding, or error behavior. With annotations covering safety, this is adequate but not rich.

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?

The description is a single sentence with no filler, and the operation and formula are front-loaded. It is appropriately sized for a simple calculation tool.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple read-only calculator with four required numeric inputs and no output schema, the description supplies the essential formula. It could say more about the return value or rounding, but the core call contract is clear.

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%, and the description names all four inputs—business value, urgency, risk/opportunity, and job size—and their roles in the formula. However, it adds no scale or unit details beyond the schema titles and ranges, so it only partially compensates for the missing parameter descriptions.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and result (compute WSJF) and spells out the operation: combine relative value, urgency, and risk/opportunity, then divide by job size. This clearly identifies the tool's purpose and distinguishes it from unrelated weighted-calculation siblings.

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?

The description gives no explicit when-to-use or when-not-to-use guidance, and it names no alternatives or prerequisites. The only usage signal is the implied purpose of computing WSJF, so an agent must infer the context.

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.