Skip to main content
Glama

Agency or Internal Staffing Crossover

bpj_agency_hire_crossover
Read-onlyIdempotent

Compare hourly agency billing with a fixed-plus-variable internal team and find the service-hour crossover.

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": {
      "agency": "<agency>",
      "agencyHours": "<agencyHours>",
      "employee": "<employee>",
      "variable": "<variable>"
    },
    "name": "bpj_agency_hire_crossover"
  }
}

Input Schema

NameRequiredDescriptionDefault
agencyYes
employeeYes
variableYes
agencyHoursYes

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 read-only, idempotent, non-destructive, and closed-world behavior, so the safety profile is covered. The description adds that this is a comparison calculation returning a crossover, but it omits calculation assumptions, formula, and output precision.

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 is appropriately terse for a calculation tool, though its brevity contributes to other gaps.

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 four-parameter calculation with no output schema and no schema parameter descriptions, the definition is incomplete. An agent can infer the broad comparison, but key formula assumptions and full input/output semantics are missing.

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?

With 0% schema description coverage and four required parameters, the description does not explain each input's role in detail. It hints at agency hourly cost, internal fixed cost, variable cost per hour, and service hours, but does not clarify the monthly basis, required inputs, or how the crossover is computed.

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?

States a specific comparison and result: hourly agency billing vs a fixed-plus-variable internal team, and the service-hour crossover. Clear enough to select, but it does not explicitly differentiate its role from similar crossover or staffing 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?

Gives no explicit when-to-use or when-not-to-use guidance, no prerequisites, and no alternatives among sibling staffing or crossover tools. The only usage information is implied by the comparison purpose.

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.