Skip to main content
Glama

Blended Team Labor Rate

bpj_mixed_team_labor_rate
Read-onlyIdempotent

Weight the pay rates of two labor groups by hours worked to calculate project cost and a blended hourly rate.

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": {
      "hoursA": "<hoursA>",
      "rate": "<rate>",
      "hoursB": "<hoursB>",
      "rateB": "<rateB>"
    },
    "name": "bpj_mixed_team_labor_rate"
  }
}

Input Schema

NameRequiredDescriptionDefault
rateYes
rateBYes
hoursAYes
hoursBYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive, and closed-world behavior. The description adds the calculation performed—hour-weighted blending to produce project cost and a blended rate—but does not cover numeric edge cases or output precision. That is useful behavioral context beyond 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, front-loaded sentence with no filler. It efficiently communicates the calculation.

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 four-parameter pure calculator with no output schema, the description explains both the inputs' relationship and the two outputs. It is nearly complete; only unit and precision details are absent, which are minor for this tool type.

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 explains that the rates belong to two labor groups and are weighted by hours worked, which maps conceptually to rate/rateB and hoursA/hoursB, but it does not clarify units, currency, or which rate is Group A beyond the schema titles.

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 computational action ('Weight the pay rates of two labor groups by hours worked') and names both outputs ('project cost and a blended hourly rate'). It does not differentiate from sibling labor-cost tools, so it is a 4 rather than a 5.

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?

No explicit when-to-use guidance or alternatives are given. An agent must infer that this is for blending exactly two groups' rates, and there is no mention of related sibling tools like bpj_meeting_labor_cost.

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.