Skip to main content
Glama

Customer Service Cost Ceiling

bpj_customer_support_cost_ceiling
Read-onlyIdempotent

Calculate the monthly contribution available for other costs after account-level servicing expenses.

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": {
      "active": "<active>",
      "monthly": "<monthly>",
      "support": "<support>"
    },
    "name": "bpj_customer_support_cost_ceiling"
  }
}

Input Schema

NameRequiredDescriptionDefault
activeYes
monthlyYes
supportYes

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 establish that this is a read-only, idempotent, non-destructive calculation with closed-world behavior. The description adds that the result is a monthly contribution after servicing expenses, but it does not disclose the exact formula, assumptions, or output units beyond that high-level framing.

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?

The definition is a single front-loaded sentence with no wasted wording. It states the calculation target immediately and remains easy to parse.

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 pure calculation tool with three required parameters and no output schema, the definition is incomplete because it omits the formula, output interpretation, and units. The annotations cover safety, but they do not make up for the missing calculation details.

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 compensate by explaining the three required inputs. It does not map the parameters to the calculation or clarify how active accounts, month-to-month price, and service cost per account combine.

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 uses a specific verb and resource: calculating the monthly contribution available for other costs after account-level servicing expenses. It is clearer than a tautology and gives a usable sense of the metric, though it does not explicitly distinguish the tool from sibling cost and ceiling calculations.

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 stated exclusions or preconditions. The only usage signal is implicit from the calculation context.

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.