Skip to main content
Glama

Unused Seat License Reclamation

bpj_seat_license_reclamation
Read-onlyIdempotent

Identify unactivated seats and estimate the monthly spend recoverable if those seats can be removed at renewal.

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": {
      "seats": "<seats>",
      "used": "<used>",
      "seatPrice": "<seatPrice>"
    },
    "name": "bpj_seat_license_reclamation"
  }
}

Input Schema

NameRequiredDescriptionDefault
usedYes
seatsYes
seatPriceYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already establish that the tool is read-only, idempotent, and non-destructive. The description adds valuable behavioral context by framing the result as an estimate under a renewal condition and by clarifying that it identifies unactivated seats rather than performing removal, which prevents confusion from the 'reclamation' name.

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 description is a single front-loaded sentence with no redundant wording. Every phrase contributes to the purpose or the conditional nature of the estimate.

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

Completeness3/5

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

For a simple three-parameter calculation, the description covers the core purpose and the conditional nature of the output. However, it does not explain how the inputs combine, what units or constraints apply, or what the return value contains, which matters given the absence of an output schema and 0% schema description coverage.

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 for undocumented parameters, but it never names or defines seats, used, or seatPrice. It only implies the concepts of unactivated seats and monthly spend, leaving the mapping between those concepts and the three required inputs to inference.

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 analytical purpose: identify unactivated seats and estimate monthly recoverable spend. It is clear what the tool computes, but it does not distinguish itself from sibling tools such as bpj_release_license_notices or explain when this estimation differs from actual license release workflows.

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 through the renewal context and the conditional 'if those seats can be removed at renewal,' but there is no explicit when-to-use guidance or comparison to alternatives. An agent can infer this is for pre-renewal savings estimates, yet no exclusions or prerequisites are stated.

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.