Skip to main content
Glama
Sign In

Brief

by cards.getbrief
OverviewDiscussionsAdmin

Dated bank changes

list_changes
Read-onlyIdempotent

Changes banks have made to card rules since a date: devaluations, fee changes, lounge gates, transfer partners added or removed, improvements. Newest first, upcoming ones included and marked. Each change carries the date it takes effect, the cards it touches, grade, check date, source and its own page on getbrief.cards.

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": {
      "since": "<since>"
    },
    "name": "list_changes"
  }
}

Input Schema

NameRequiredDescriptionDefault
cardNoOnly changes touching this card.
limitNoAt most this many changes. 20 if unset.
sinceYesChanges taking effect on or after this date, YYYY-MM-DD.
untilNoAnd on or before this date.
issuerNoOne bank.
severityNoOne kind of change: devaluation, fee_change, lounge_gating, partner_removed, partner_added, retention_rule, enhancement. enhancement is an improvement.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / severity / description
      Added value: +"One kind of change: devaluation, fee_change, lounge_gating, partner_removed, partner_added, retention_rule, enhancement. enhancement is an improvement."
  2. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive, closed-world), and the description adds real behavioral value: ordering is newest-first, upcoming/future-dated changes are included and flagged, and each record carries effective date, affected cards, grade, check date, source and a permalink. It stops short of describing pagination or what happens when no changes match.

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?

Two sentences, front-loaded with the resource and scope, followed by result-shape details. Dense but every clause carries information; minor tightening of the long first sentence would help, but nothing is filler.

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?

With no output schema, the description usefully compensates by describing the shape and ordering of returned changes. Combined with 100% schema coverage and clear annotations, the definition is sufficient to call correctly; only default limit behavior and empty-result handling are left implicit.

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 coverage is 100%, so all six filters (card, issuer, severity, since, until, limit) are already self-documenting, including two enums. The description only reinforces the date scoping and the 'upcoming included' nuance; it adds no new filter semantics beyond the schema. 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 resource (bank changes to card rules) and enumerates the kinds of change covered – devaluations, fee changes, lounge gates, transfer partners added/removed, improvements – with the 'since a date' scope. This makes it unmistakably distinct from get_card, search_cards, recommend and transfer_partners.

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?

Usage is implied by the 'since a date' framing and the change-type enumeration, which tells an agent this is the feed for 'what changed recently'. However, there is no explicit when-to-use/when-not guidance and no named alternative (e.g. 'for a card's current terms use get_card').

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

All Brief 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