Skip to main content
Glama

Launch Delay Contribution Cost

bpj_launch_delay_contribution
Read-onlyIdempotent

Combine weekly contribution forgone during a launch delay with a one-time penalty triggered by any delay.

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": {
      "weeks": "<weeks>",
      "weekly": "<weekly>",
      "penalty": "<penalty>"
    },
    "name": "bpj_launch_delay_contribution"
  }
}

Input Schema

NameRequiredDescriptionDefault
weeksYes
weeklyYes
penaltyYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already establish that this is a read-only, idempotent, closed calculation with no destructive effects. The description adds useful context by explaining that the cost combines recurring weekly contribution loss with a one-time penalty, but it does not clarify edge cases such as whether the penalty applies when weeks is zero or how the total is returned.

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?

It is a single, front-loaded sentence with no unnecessary wording. The core calculation components are stated immediately.

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 simple three-parameter calculator, the description conveys the main cost components and annotations cover safety behavior. However, it leaves the exact combination rule and the handling of zero-delay or penalty applicability ambiguous.

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%, but the schema titles already label the parameters as delay weeks, weekly contribution lost, and one-time penalty. The description reinforces those meanings but does not state the exact formula or clarify the relationship between weeks and weekly contribution.

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 states a specific calculation: combining weekly contribution forgone during a launch delay with a one-time delay penalty. This clearly identifies the tool's purpose, though it does not differentiate it from the many sibling contribution/cost calculators.

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 explicit guidance on when to use this tool versus alternatives, nor any prerequisites or exclusions. The name and description imply it is a launch-delay cost calculator, but usage remains inferred rather than stated.

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.