mcp-tools

AI subscription stack cost

ai_subscription_stack_cost

Read-onlyIdempotent

Calculate monthly and annual USD totals for selected AI chat and coding subscriptions and identify overlapping capabilities. Use to review your subscription stack.

Instructions

Total selected AI chat and coding subscriptions in USD and identify overlapping capabilities. Use to review a subscription stack; use ai_api_cost for API token charges. Select unique planIds from the schema enum; [] returns zero totals and no plans. Returns monthly and annual totals, selected plans, capability groups and dated official sources. Annual totals use published annual billing or twelve monthly charges; taxes, regional differences and promotions are excluded. Bundled rates are dated estimates, without live billing lookup or subscription changes.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`planIds`	Yes	Unique subscription IDs from the enum. An empty list returns zero totals and no selected plans.

Output Schema

TableJSON Schema

Name	Required	Description
`tool`	Yes	Calculator identifier for this result.
`input`	Yes	Normalized inputs used for this calculation.
`plans`	Yes	Selected plans with published USD charges and dated sources, in input order.
`units`	Yes	Units for the numeric and time fields in this result.
`method`	Yes	Calculation or ranking method applied to the inputs.
`overlap`	Yes	Capability groups and selected plan IDs; more than one plan ID indicates overlap.
`provenance`	Yes	Dated data sources or runtime time-zone information used for this result.
`annualTotal`	Yes	Sum of published annual charges or twelve monthly charges per plan; excludes taxes, regional changes and promotions.
`assumptions`	Yes	Limits and assumptions to retain when presenting the result.
`monthlyTotal`	Yes	Sum of selected monthly USD charges; zero for an empty stack.

Schema Changelog

Changes observed during successful MCP inspections.

Changed39 schema fields changedv1.1.0Oct 3, 2026
- addedInput schema / properties / planIds / description
```
Added value: +"Unique subscription IDs from the enum. An empty list returns zero totals and no selected plans."
```
- addedInput schema / properties / planIds / examples
```
Added value: +[
+  [
+    "chatgpt-plus",
+    "claude-pro"
+  ],
+  []
+]
```
- addedInput schema / properties / planIds / items / description
```
Added value: +"ID of a plan in the bundled subscription catalog."
```
- addedOutput schema / description
```
Added value: +"Subscription totals, capability overlap and dated plan sources with normalized selection."
```
- addedOutput schema / properties / annualTotal / description
```
Added value: +"Sum of published annual charges or twelve monthly charges per plan; excludes taxes, regional changes and promotions."
```
- addedOutput schema / properties / assumptions / description
```
Added value: +"Limits and assumptions to retain when presenting the result."
```
- addedOutput schema / properties / input / description
```
Added value: +"Normalized inputs used for this calculation."
```
- addedOutput schema / properties / input / properties / planIds / description
```
Added value: +"Unique subscription IDs from the enum. An empty list returns zero totals and no selected plans."
```
- addedOutput schema / properties / input / properties / planIds / examples
```
Added value: +[
+  [
+    "chatgpt-plus",
+    "claude-pro"
+  ],
+  []
+]
```
- addedOutput schema / properties / input / properties / planIds / items / description
```
Added value: +"ID of a plan in the bundled subscription catalog."
```
- addedOutput schema / properties / method / description
```
Added value: +"Calculation or ranking method applied to the inputs."
```
- addedOutput schema / properties / monthlyTotal / description
```
Added value: +"Sum of selected monthly USD charges; zero for an empty stack."
```
- addedOutput schema / properties / overlap / description
```
Added value: +"Capability groups and selected plan IDs; more than one plan ID indicates overlap."
```
- addedOutput schema / properties / overlap / items / properties / id / description
```
Added value: +"Catalog identifier for a plan or capability."
```
- addedOutput schema / properties / overlap / items / properties / label / description
```
Added value: +"Human-readable capability label."
```
- addedOutput schema / properties / overlap / items / properties / planIds / description
```
Added value: +"Selected plans offering this capability; more than one ID indicates overlap."
```
- addedOutput schema / properties / plans / description
```
Added value: +"Selected plans with published USD charges and dated sources, in input order."
```
- addedOutput schema / properties / plans / items / properties / annual / description
```
Added value: +"Published USD annual charge; null if only monthly billing is listed."
```
- addedOutput schema / properties / plans / items / properties / annualNote / description
```
Added value: +"Qualification about annual billing."
```
- addedOutput schema / properties / plans / items / properties / capabilities / additionalProperties / description
```
Added value: +"Whether the plan offers this capability."
```
- addedOutput schema / properties / plans / items / properties / capabilities / description
```
Added value: +"Capability IDs mapped to whether the selected plan includes them."
```
- addedOutput schema / properties / plans / items / properties / checked / description
```
Added value: +"Date the referenced catalog or scheduler source was checked."
```
- addedOutput schema / properties / plans / items / properties / id / description
```
Added value: +"Catalog identifier for a plan or capability."
```
- addedOutput schema / properties / plans / items / properties / modelFamilies / description
```
Added value: +"Model family labels listed for the plan."
```
- addedOutput schema / properties / plans / items / properties / modelSource / description
```
Added value: +"Official source for plan model access."
```
- addedOutput schema / properties / plans / items / properties / monthly / description
```
Added value: +"Published USD monthly charge."
```
- addedOutput schema / properties / plans / items / properties / name / description
```
Added value: +"Display name of the selected model or plan."
```
- addedOutput schema / properties / plans / items / properties / provider / description
```
Added value: +"Public subscription provider name."
```
- addedOutput schema / properties / plans / items / properties / source / description
```
Added value: +"Official plan pricing URL."
```
- addedOutput schema / properties / plans / items / properties / sourceNote / description
```
Added value: +"Qualification about the source or plan availability."
```
- addedOutput schema / properties / provenance / description
```
Added value: +"Dated data sources or runtime time-zone information used for this result."
```
- addedOutput schema / properties / provenance / properties / checked / description
```
Added value: +"Date the referenced catalog or scheduler source was checked."
```
- addedOutput schema / properties / provenance / properties / sources / description
```
Added value: +"Official pricing sources for the selected plans."
```
- addedOutput schema / properties / provenance / properties / sources / items / properties / checked / description
```
Added value: +"Date the referenced catalog or scheduler source was checked."
```
- addedOutput schema / properties / provenance / properties / sources / items / properties / planId / description
```
Added value: +"Selected plan ID corresponding to this source."
```
- addedOutput schema / properties / provenance / properties / sources / items / properties / url / description
```
Added value: +"Official plan pricing URL."
```
- addedOutput schema / properties / tool / description
```
Added value: +"Calculator identifier for this result."
```
- addedOutput schema / properties / units / description
```
Added value: +"Units for the numeric and time fields in this result."
```
- addedOutput schema / properties / units / properties / totals / description
```
Added value: +"Currency for subscription totals."
```
First observedv1.0.0Oct 2, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Goes well beyond the annotations (which only cover read-only/idempotent/no-write): it discloses how annual totals are derived, that taxes/regional differences/promotions are excluded, that bundled rates are dated estimates, and that no live billing lookup or subscription mutation occurs. That is exactly the behavioral context an agent needs before quoting numbers to a user.

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?

Five dense sentences with no filler, and the primary purpose plus sibling routing are front-loaded. It is information-heavy and could use light grouping, but every sentence carries operational information.

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

Completeness5/5

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

An output schema exists, so return values need not be described, yet the description still sketches the return shape (totals, selected plans, capability groups, dated sources) and bounds the accuracy of its numbers. Nothing material is missing for invoking this correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and the enum already enumerates valid planIds, so the baseline is 3. The description adds genuine meaning beyond the schema: the 'unique' constraint, the empty-list semantics ('[] returns zero totals'), and the requirement to select IDs from the enum rather than free-text plan names.

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

Purpose5/5

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

States a specific verb+resource (compute total cost of selected AI chat/coding subscriptions) plus the analytical add-on (identify overlapping capabilities). It explicitly distinguishes itself from the sibling ai_api_cost, so an agent can route without opening either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Names the scenario ('use to review a subscription stack') and the alternative with its condition ('use ai_api_cost for API token charges'). It also covers the degenerate input case ('[] returns zero totals and no plans'), leaving little to inference.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server