Skip to main content
Glama

Shared Resource Overbooking

bpj_project_resource_overbooking
Read-onlyIdempotent

Combine two project commitments on a shared weekly resource and quantify overbooking or spare capacity.

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": {
      "workA": "<workA>",
      "workB": "<workB>",
      "divider": "<divider>"
    },
    "name": "bpj_project_resource_overbooking"
  }
}

Input Schema

NameRequiredDescriptionDefault
workAYes
workBYes
dividerYes

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, idempotentHint, non-destructive, and closed-world, so the safety profile is fully covered. The description adds that the computation is a comparison of two commitments against one capacity, but it does not state what the result looks like (hours over, percentage, sign convention) or how a zero capacity behaves despite 'divider' allowing 0. Useful context, not rich context.

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 zero filler; the purpose and the two-part outcome are stated up front. Its brevity edges toward under-specification rather than waste, but there is no redundant wording to cut.

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 three-number, read-only calculator with no output schema and annotations covering safety, this is close to sufficient. The remaining gap is the result semantics and the zero-capacity edge case, which an agent would want before invoking it with divider=0.

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 convey units and roles ('Project A hours this week', 'Shared resource weekly capacity'). The description confirms the mapping of workA/workB to commitments and divider to capacity, which disambiguates divider as a capacity rather than a divisor factor. It adds no unit, format, or boundary guidance beyond that.

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?

Uses specific verbs (combine, quantify) against a named resource (two project commitments on a shared weekly resource) plus the outcome (overbooking or spare capacity), so the operation is immediately identifiable. It does not explicitly differentiate itself from any sibling, but the sibling catalog is dominated by unrelated finance/encoding calculators, so the gap is minor.

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 framing: supply two weekly workloads and a shared capacity to get an overbooking figure. There is no explicit statement of when to prefer this over a headroom or commitment tool, and no preconditions or exclusions are given, leaving the agent to infer the trigger from the name alone.

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.