Skip to main content
Glama
Sign In
wealth-engine

wealth-engine

by Jaume9
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Subscription Audit & Savings Finder

subscription_audit

Audit your recurring subscriptions: annualize costs, compute cost-per-use, and identify low-value services to cut, showing exactly how much you can save each year.

Instructions

Audit recurring subscriptions: annualize every line, compute cost-per-use, and flag low-value or rarely used services as candidates to cut — quantifying exactly how much money you can recover per year.

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": {
      "subscriptions": "<subscriptions>"
    },
    "name": "subscription_audit"
  }
}

Input Schema

NameRequiredDescriptionDefault
subscriptionsYesYour subscriptions.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4/5.0
Behavior3/5

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

No annotations provided; the description carries full burden. It explains the analysis performed but does not disclose side effects, auth needs, or that the tool is read-only. Adequate but not thorough.

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?

Single sentence front-loads the purpose and lists key actions without waste. Every phrase earns its place.

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

Completeness4/5

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

Given no output schema, the description adequately conveys the return value (quantified savings) and the overall process. Could benefit from mentioning output format or prerequisites, but sufficient for an analysis tool.

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%, baseline 3. The description adds value by explaining how parameters are used in computations (annualization, cost-per-use, low-value flags), providing meaningful context beyond field 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?

The description uses a specific verb 'Audit' and resource 'recurring subscriptions', detailing actions: annualize, compute cost-per-use, flag low-value, quantify savings. It clearly distinguishes from sibling tools like budget_analyzer or debt_payoff.

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 description implies usage for auditing subscriptions to find savings, but does not explicitly state when to use this over alternatives or give exclusions. Lacks comparative guidance,

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

Deploy Server

Other Tools