Skip to main content
Glama

Recurring Meeting Cost

bpj_meeting_labor_cost
Read-onlyIdempotent

Calculate participant-hours and labor cost for recurring meetings, including preparation.

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": {
      "participants": "<participants>",
      "count": "<count>",
      "meetingMinutes": "<meetingMinutes>",
      "preparationMinutes": "<preparationMinutes>",
      "hourlyCost": "<hourlyCost>"
    },
    "name": "bpj_meeting_labor_cost"
  }
}

Input Schema

NameRequiredDescriptionDefault
countYes
hourlyCostYes
participantsYes
meetingMinutesYes
preparationMinutesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare this as read-only, idempotent, closed-world, and non-destructive. The description adds useful behavioral context that preparation time is included in the calculation, but it does not explain whether preparation is applied per person per meeting, how recurring count affects totals, or any rounding/format behavior.

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 unnecessary wording. It states the calculation and the preparation inclusion efficiently.

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

Completeness2/5

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

For a five-required-parameter calculator with no output schema and no parameter descriptions, the definition is too thin. It does not explain how the inputs combine into participant-hours and labor cost, nor how preparation and recurring count affect the result.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/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 hints at participants, recurring count, labor cost, meeting duration, and preparation through the output concepts, but does not clarify key semantics such as whether preparation minutes are per person per meeting or whether count multiplies the total.

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 gives a specific verb and resource: calculate participant-hours and labor cost for recurring meetings with preparation. It is clear what the tool produces, though it does not explicitly situate itself relative to siblings (the listed siblings appear unrelated in domain).

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 when-to-use or when-not-to-use guidance, no prerequisites, and no alternatives named. The phrase 'for recurring meetings' implies scope but does not actively guide tool selection.

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.