Skip to main content
Glama

Subscriber Steady State

bpj_subscriber_steady_state
Read-onlyIdempotent

Estimate the equilibrium subscriber count when a fixed number join each month and a constant share of existing accounts churn.

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": {
      "newAccounts": "<newAccounts>",
      "churnRate": "<churnRate>",
      "monthly": "<monthly>"
    },
    "name": "bpj_subscriber_steady_state"
  }
}

Input Schema

NameRequiredDescriptionDefault
monthlyYes
churnRateYes
newAccountsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare the operation as read-only, idempotent, non-destructive, and closed-world. The description adds useful model context (fixed new accounts, constant churn share), but it does not describe the return value, rounding behavior, or edge-case handling such as zero churn or zero new accounts.

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. Every phrase contributes to describing the calculation model.

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 simple three-parameter calculator with no output schema, the description should explain all inputs and the returned equilibrium count. It omits the 'monthly' parameter entirely and does not state what the output represents.

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, the description must carry parameter meaning. It loosely explains 'newAccounts' and 'churnRate', but it completely omits the 'monthly' parameter, leaving a required input unexplained. Units (e.g., churn as a percentage) and formats are also not clarified.

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 verb ('Estimate') and resource ('equilibrium subscriber count') along with the model assumptions. It is clear what the tool computes, though it does not explicitly differentiate itself from any sibling tool.

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?

The described scenario (fixed monthly joins and constant churn share) implies when the tool applies, but there is no explicit 'use this when' guidance, no alternatives, and no exclusions. The usage is inferable but not spelled out.

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.