Skip to main content
Glama

Free Trial Subsidy

bpj_free_trial_subsidy
Read-onlyIdempotent

Spread the cost of serving all eligible trials over those becoming paid and show activation-to-paid conversion.

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": {
      "leads": "<leads>",
      "activated": "<activated>",
      "paid": "<paid>",
      "daysFree": "<daysFree>",
      "perDay": "<perDay>"
    },
    "name": "bpj_free_trial_subsidy"
  }
}

Input Schema

NameRequiredDescriptionDefault
paidYes
leadsYes
perDayYes
daysFreeYes
activatedYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.4/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is fully covered by structured data. The description adds no behavioral context beyond that: it doesn't state the computation's assumptions (e.g. whether every eligible trial accrues perDay cost for daysFree), units or currency, handling of zero paid conversions, or what the response contains.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence with no filler or repetition. It is efficient, though the compression contributes to the ambiguity noted above rather than resolving it.

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?

This is a five-required-parameter financial calculator with no output schema and 0% schema description coverage, so the description needs to define the computation and the inputs. It provides neither the formula nor the meaning of two parameters, leaving an agent unable to invoke it correctly except by guessing.

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% – only titles exist – so the description must carry parameter meaning, and it largely doesn't. It alludes to 'eligible trials' (leads) and 'those becoming paid' (paid) and hints at activated via 'activation-to-paid conversion', but daysFree and perDay receive no mention and no formula links the five inputs to an output.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a recognizable operation ('spread the cost of serving all eligible trials over those becoming paid') and a secondary output ('show activation-to-paid conversion'), so the general gist is graspable. However, the phrasing is abstract enough that an agent cannot confidently predict what value is returned (a per-paid-account subsidy? a total subsidized cost? a ratio?). It does not clearly distinguish itself from numeric siblings like bpj_trial_balance_difference.

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 when-to-use guidance, no prerequisites, and no indication of when a different calculator would be the right choice. The agent must infer usage entirely from the name and one sentence.

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.