Skip to main content
Glama

Audit fees

audit_fees
Read-onlyIdempotent

Audit a list of fees: annualize each one (monthly x12), total the yearly cost and monthly average, and flag charges above the typical US range for their category, duplicate names and one-time fees of $30+ worth disputing. Use when the user lists fees to review. For a multi-year projection use annual_cost; for typical ranges alone use benchmark_fees.

Input Schema

NameRequiredDescriptionDefault
feesYesNon-empty list of fees to audit, each {name, amount, frequency, category?}

Output Schema

NameRequiredDescriptionDefault
feesYesOne audited row per input fee, in input order
noteYesPlain-language summary of the audit result; lists any unknown category keys that were ignored
currencyYesCurrency of all amounts; always USD
total_annualYesSum of all annualized fees, USD
flagged_countYesNumber of fees with at least one flag
total_monthly_averageYestotal_annual divided by 12, USD

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / fees / items / properties / category / description
      Previous value: -"Optional benchmark category key (case-insensitive; spaces/hyphens become underscores). One of: bank_overdraft, bank_monthly_maintenance, atm_out_of_network, late_payment, gym_membership_monthly, streaming_monthly, airline_checked_bag, airline_seat_fee, ticket_convenience, rental_application, subscription_app_monthly, delivery_fee, airline_change_fee, hotel_resort_fee. Unknown keys are ignored."New value: +"Optional benchmark category key (case-insensitive; spaces/hyphens become underscores). One of: bank_overdraft, bank_monthly_maintenance, atm_out_of_network, late_payment, gym_membership_monthly, streaming_monthly, airline_checked_bag, airline_seat_fee, ticket_convenience, rental_application, subscription_app_monthly, delivery_fee, airline_change_fee, hotel_resort_fee. Unknown keys are ignored for benchmarking and listed in audit_fees' note."
    • changedOutput schema / properties / note / description
      Previous value: -"Plain-language summary of the audit result"New value: +"Plain-language summary of the audit result; lists any unknown category keys that were ignored"
  2. Changed9 schema fields changed
    • changedInput schema / properties / fees / description
      Previous value: -"Fees to audit, each with name, amount, frequency and optional category"New value: +"Non-empty list of fees to audit, each {name, amount, frequency, category?}"
    • changedInput schema / properties / fees / items / properties / amount / description
      Previous value: -"Amount charged in USD"New value: +"Amount per charge in USD, greater than 0, e.g. 38 or 15.99 (for monthly fees, the monthly amount)"
    • addedInput schema / properties / fees / items / properties / amount / exclusiveMinimum
      Added value: +0
    • changedInput schema / properties / fees / items / properties / category / description
      Previous value: -"Optional benchmark category key, e.g. bank_overdraft"New value: +"Optional benchmark category key (case-insensitive; spaces/hyphens become underscores). One of: bank_overdraft, bank_monthly_maintenance, atm_out_of_network, late_payment, gym_membership_monthly, streaming_monthly, airline_checked_bag, airline_seat_fee, ticket_convenience, rental_application, subscription_app_monthly, delivery_fee, airline_change_fee, hotel_resort_fee. Unknown keys are ignored."
    • changedInput schema / properties / fees / items / properties / frequency / description
      Previous value: -"How often the fee recurs"New value: +"How often the fee is charged: 'monthly' (x12 per year), 'annual' or 'one-time'"
    • changedInput schema / properties / fees / items / properties / name / description
      Previous value: -"Fee description, e.g. 'Overdraft fee'"New value: +"Fee label as it appears on the statement, e.g. 'Overdraft fee' or 'Netflix'"
    • addedInput schema / properties / fees / items / properties / name / minLength
      Added value: +1
    • addedInput schema / properties / fees / minItems
      Added value: +1
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "currency": {
      +      "description": "Currency of all amounts; always USD",
      +      "type": "string"
      +    },
      +    "fees": {
      +      "description": "One audited row per input fee, in input order",
      +      "items": {
      +        "properties": {
      +          "amount": {
      +            "description": "Amount per charge, USD, rounded to cents",
      +            "type": "number"
      +          },
      +          "annualized": {
      +            "description": "Yearly cost of this fee, USD (monthly x12; annual and one-time as-is)",
      +            "type": "number"
      +          },
      +          "flags": {
      +            "description": "Problem flags; empty when none apply",
      +            "items": {
      +              "enum": [
      +                "above typical",
      +                "duplicate name",
      +                "worth disputing"
      +              ],
      +              "type": "string"
      +            },
      +            "type": "array"
      +          },
      +          "frequency": {
      +            "description": "Charge frequency as given",
      +            "enum": [
      +              "monthly",
      +              "annual",
      +              "one-time"
      +            ],
      +            "type": "string"
      +          },
      +          "name": {
      +            "description": "Trimmed fee name",
      +            "type": "string"
      +          }
      +        },
      +        "required": [
      +          "name",
      +          "amount",
      +          "frequency",
      +          "annualized",
      +          "flags"
      +        ],
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    "flagged_count": {
      +      "description": "Number of fees with at least one flag",
      +      "type": "integer"
      +    },
      +    "note": {
      +      "description": "Plain-language summary of the audit result",
      +      "type": "string"
      +    },
      +    "total_annual": {
      +      "description": "Sum of all annualized fees, USD",
      +      "type": "number"
      +    },
      +    "total_monthly_average": {
      +      "description": "total_annual divided by 12, USD",
      +      "type": "number"
      +    }
      +  },
      +  "required": [
      +    "currency",
      +    "fees",
      +    "total_annual",
      +    "total_monthly_average",
      +    "flagged_count",
      +    "note"
      +  ],
      +  "type": "object"
      +}
  3. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -{
      -  "properties": {
      -    "annualizedFees": {
      -      "description": "A list of fees with their annualized amounts.",
      -      "items": {
      -        "properties": {
      -          "annualizedAmount": {
      -            "description": "The annualized amount of the fee.",
      -            "type": "number"
      -          },
      -          "name": {
      -            "description": "The name of the fee.",
      -            "type": "string"
      -          }
      -        },
      -        "required": [
      -          "name",
      -          "annualizedAmount"
      -        ],
      -        "type": "object"
      -      },
      -      "type": "array"
      -    },
      -    "flags": {
      -      "description": "A list of flags indicating issues with specific fees.",
      -      "items": {
      -        "properties": {
      -          "details": {
      -            "description": "Additional details about the flagged issue.",
      -            "type": "string"
      -          },
      -          "issue": {
      -            "description": "The type of issue flagged for the fee.",
      -            "enum": [
      -              "above_typical_range",
      -              "duplicate_name",
      -              "disputable_one_time"
      -            ],
      -            "type": "string"
      -          },
      -          "name": {
      -            "description": "The name of the fee that triggered the flag.",
      -            "type": "string"
      -          }
      -        },
      -        "required": [
      -          "name",
      -          "issue"
      -        ],
      -        "type": "object"
      -      },
      -      "type": "array"
      -    },
      -    "monthlyAverage": {
      -      "description": "The average monthly cost of all fees.",
      -      "type": "number"
      -    },
      -    "totalYearlyCost": {
      -      "description": "The sum of all annualized fees.",
      -      "type": "number"
      -    }
      -  },
      -  "required": [
      -    "totalYearlyCost",
      -    "monthlyAverage",
      -    "flags",
      -    "annualizedFees"
      -  ],
      -  "type": "object"
      -}New value: +null
  4. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "annualizedFees": {
      +      "description": "A list of fees with their annualized amounts.",
      +      "items": {
      +        "properties": {
      +          "annualizedAmount": {
      +            "description": "The annualized amount of the fee.",
      +            "type": "number"
      +          },
      +          "name": {
      +            "description": "The name of the fee.",
      +            "type": "string"
      +          }
      +        },
      +        "required": [
      +          "name",
      +          "annualizedAmount"
      +        ],
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    "flags": {
      +      "description": "A list of flags indicating issues with specific fees.",
      +      "items": {
      +        "properties": {
      +          "details": {
      +            "description": "Additional details about the flagged issue.",
      +            "type": "string"
      +          },
      +          "issue": {
      +            "description": "The type of issue flagged for the fee.",
      +            "enum": [
      +              "above_typical_range",
      +              "duplicate_name",
      +              "disputable_one_time"
      +            ],
      +            "type": "string"
      +          },
      +          "name": {
      +            "description": "The name of the fee that triggered the flag.",
      +            "type": "string"
      +          }
      +        },
      +        "required": [
      +          "name",
      +          "issue"
      +        ],
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    "monthlyAverage": {
      +      "description": "The average monthly cost of all fees.",
      +      "type": "number"
      +    },
      +    "totalYearlyCost": {
      +      "description": "The sum of all annualized fees.",
      +      "type": "number"
      +    }
      +  },
      +  "required": [
      +    "totalYearlyCost",
      +    "monthlyAverage",
      +    "flags",
      +    "annualizedFees"
      +  ],
      +  "type": "object"
      +}
  5. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds real behavioral substance on top: the annualization formula (monthly x12), the aggregations produced, and the specific flagging thresholds (above typical US range, duplicate names, one-time fees of $30+). It does not discuss error handling for malformed fee entries, but the output schema carries the return shape.

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?

Two sentences, zero filler. The core computation is front-loaded before the routing guidance, and every clause (annualization, totals, flag rules, alternatives) carries information an agent needs.

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, and the description still covers the computation, aggregation and flagging semantics plus sibling routing. Nothing material is missing for an agent to call this correctly.

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

Parameters3/5

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

Schema description coverage is 100% for the single fees parameter, including nested name/amount/category/frequency documentation and the benchmark category key list, so the baseline is 3. The description restates the monthly x12 rule and adds the $30 one-time threshold, which is a marginal gain over what the schema already documents.

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 (audit) and resource (list of fees) and spells out the exact operations performed: annualize monthly x12, total yearly cost and monthly average, and flag outliers, duplicates and disputable one-time fees. It also names what it is not by pointing to annual_cost and benchmark_fees, so an agent can separate it from siblings without opening any 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?

Gives an explicit trigger ('Use when the user lists fees to review') plus two named alternatives with the exact condition that selects each: multi-year projection -> annual_cost, typical ranges alone -> benchmark_fees. Both the when and the when-not are covered.

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.

Resources