Skip to main content
Glama

FeeFighter

by io.github.everyai-com
OverviewDiscussionsAdmin

Benchmark fees

benchmark_fees
Read-onlyIdempotent

Look up typical US consumer fee ranges (min/max per charge, USD) for one category such as bank_overdraft, or the full 14-category table when category is omitted. Use to answer 'is this fee normal?' questions. To check a user's own list of fees against these ranges, use audit_fees.

Input Schema

NameRequiredDescriptionDefault
categoryNoCategory 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. Omit to get the full table; an unknown key returns an error listing valid keys.

Output Schema

NameRequiredDescriptionDefault
basisNoBasis label for the range (typical US range - verify current pricing)
countNoNumber of categories (full-table response only)
labelNoHuman-readable fee label, e.g. 'Out-of-network ATM fee'
categoryNoBenchmark category key, e.g. bank_overdraft
currencyYesCurrency of all ranges; always USD
categoriesNoEvery benchmark row (full-table response only)
disclaimerYesInformational-only disclaimer
source_noteYesWhere the ranges come from and how to read them
typical_maxNoHigh end of the typical US range per charge, USD
typical_minNoLow end of the typical US range per charge, USD

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / category / description
      Previous value: -"Category key to look up, e.g. bank_overdraft; omit for the full table"New value: +"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. Omit to get the full table; an unknown key returns an error listing valid keys."
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "basis": {
+      "description": "Basis label for the range (typical US range - verify current pricing)",
+      "type": "string"
+    },
+    "categories": {
+      "description": "Every benchmark row (full-table response only)",
+      "items": {
+        "properties": {
+          "basis": {
+            "description": "Basis label for the range (typical US range - verify current pricing)",
+            "type": "string"
+          },
+          "category": {
+            "description": "Benchmark category key, e.g. bank_overdraft",
+            "type": "string"
+          },
+          "label": {
+            "description": "Human-readable fee label, e.g. 'Out-of-network ATM fee'",
+            "type": "string"
+          },
+          "typical_max": {
+            "description": "High end of the typical US range per charge, USD",
+            "type": "number"
+          },
+          "typical_min": {
+            "description": "Low end of the typical US range per charge, USD",
+            "type": "number"
+          }
+        },
+        "required": [
+          "category",
+          "label",
+          "typical_min",
+          "typical_max",
+          "basis"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "category": {
+      "description": "Benchmark category key, e.g. bank_overdraft",
+      "type": "string"
+    },
+    "count": {
+      "description": "Number of categories (full-table response only)",
+      "type": "integer"
+    },
+    "currency": {
+      "description": "Currency of all ranges; always USD",
+      "type": "string"
+    },
+    "disclaimer": {
+      "description": "Informational-only disclaimer",
+      "type": "string"
+    },
+    "label": {
+      "description": "Human-readable fee label, e.g. 'Out-of-network ATM fee'",
+      "type": "string"
+    },
+    "source_note": {
+      "description": "Where the ranges come from and how to read them",
+      "type": "string"
+    },
+    "typical_max": {
+      "description": "High end of the typical US range per charge, USD",
+      "type": "number"
+    },
+    "typical_min": {
+      "description": "Low end of the typical US range per charge, USD",
+      "type": "number"
+    }
+  },
+  "required": [
+    "currency",
+    "source_note",
+    "disclaimer"
+  ],
+  "type": "object"
+}
  2. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -{
-  "properties": {
-    "category": {
-      "description": "The category key looked up, e.g. bank_overdraft; or 'all' if the full table was returned.",
-      "type": "string"
-    },
-    "fees": {
-      "description": "List of typical fee ranges for the category.",
-      "items": {
-        "properties": {
-          "fee_type": {
-            "description": "The specific fee type within the category, e.g. 'overdraft fee'.",
-            "type": "string"
-          },
-          "max": {
-            "description": "The maximum typical fee amount.",
-            "type": "number"
-          },
-          "min": {
-            "description": "The minimum typical fee amount.",
-            "type": "number"
-          }
-        },
-        "required": [
-          "fee_type",
-          "min",
-          "max"
-        ],
-        "type": "object"
-      },
-      "type": "array"
-    }
-  },
-  "required": [
-    "category",
-    "fees"
-  ],
-  "type": "object"
-}New value: +null
  3. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "category": {
+      "description": "The category key looked up, e.g. bank_overdraft; or 'all' if the full table was returned.",
+      "type": "string"
+    },
+    "fees": {
+      "description": "List of typical fee ranges for the category.",
+      "items": {
+        "properties": {
+          "fee_type": {
+            "description": "The specific fee type within the category, e.g. 'overdraft fee'.",
+            "type": "string"
+          },
+          "max": {
+            "description": "The maximum typical fee amount.",
+            "type": "number"
+          },
+          "min": {
+            "description": "The minimum typical fee amount.",
+            "type": "number"
+          }
+        },
+        "required": [
+          "fee_type",
+          "min",
+          "max"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "category",
+    "fees"
+  ],
+  "type": "object"
+}
  4. 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 the safe read-only/idempotent/non-destructive profile, so the bar is lower. The description adds real context: what is returned (min/max per charge in USD), the default to the full 14-category table when category is omitted, and that unknown keys error. Minor remaining gap, but it is a substantive contribution beyond the annotations.

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?

Three tight sentences with the core capability front-loaded, followed by the use case and the sibling routing. No filler and every sentence carries a distinct piece of 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?

For a read-only lookup tool with a documented parameter and an output schema covering return values, the description supplies everything the agent needs: purpose, modes, use case, and disambiguation from the sibling. Nothing essential is missing.

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% and the single category parameter, its accepted keys, case-folding rules, and the omit-for-all behavior are all documented in the schema. The description echoes the category example and fallback but adds no syntax beyond what the schema provides, so the baseline 3 applies.

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 ('look up') and resource ('typical US consumer fee ranges (min/max per charge, USD)') plus the two operating modes (single category or full 14-category table). It also names the sibling audit_fees, so an agent can distinguish it from alternatives without opening the 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?

Explicitly gives the use case ('answer is this fee normal? questions') and an exclusion with the named alternative ('to check a user's own list of fees against these ranges, use audit_fees'). When-to-use and when-to-use-something-else are both covered.

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

All FeeFighter toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources