catalog

Search the card catalog

search_card_catalog

Find credit cards open to new applicants by issuer, annual fee, network, rewards currency, or a benefit they carry. Returns a short row per card; call get_card_facts for one card's full record. Card facts only — no earning rates, welcome-offer amounts, transfer ratios, or bonus sizes.

Input Schema

TableJSON Schema

Name	Required	Description
`limit`	No	Rows to return. Default 10, maximum 25.
`issuer`	No	Exact issuer name.
`benefit`	No	Words to look for in a card's statement credits, lounge networks, or purchase/travel protections, e.g. 'Global Entry', 'Priority Pass', 'trip delay'.
`network`	No	Payment network.
`card_type`	No	Personal or Business.
`max_annual_fee`	No	Highest annual fee in dollars, inclusive.
`rewards_currency`	No	Loyalty currency the card earns, e.g. 'Chase Ultimate Rewards'. Matched loosely.
`has_lounge_access`	No	Only cards carrying at least one lounge network.
`has_free_night_certificate`	No	Only cards granting a free night certificate.
`no_foreign_transaction_fee`	No	Only cards with no foreign transaction fee.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 23, 2026

changedInput schema / properties / issuer / enum

Previous value: -[
-  "American Express",
-  "Bank of America",
-  "Barclays",
-  "BECU",
-  "Capital One",
-  "Cardless",
-  "Chase",
-  "Citi",
-  "Comenity",
-  "Discover",
-  "Elan Financial Services",
-  "Emigrant Bank",
-  "First Bank & Trust",
-  "First Electronic Bank",
-  "FNBO",
-  "Goldman Sachs",
-  "HSBC",
-  "Synchrony",
-  "TD Bank",
-  "UBS",
-  "US Bank",
-  "Wells Fargo"
-]New value: +[
+  "American Express",
+  "Bank of America",
+  "Barclays",
+  "BECU",
+  "Capital One",
+  "Chase",
+  "Citi",
+  "Column N.A.",
+  "Comenity",
+  "Discover",
+  "Elan Financial Services",
+  "Emigrant Bank",
+  "First Bank & Trust",
+  "First Electronic Bank",
+  "FNBO",
+  "Goldman Sachs",
+  "HSBC",
+  "Synchrony",
+  "TD Bank",
+  "UBS",
+  "US Bank",
+  "Wells Fargo"
+]

First observedSep 1, 2026

TDQS

A4.4/5.0

Behavior4/5

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

No annotations are provided, so the description carries the transparency burden; it handles this well by declaring the open-to-new-applicants scope, the short-row return shape, and specific excluded data categories. It does not mention result ordering or pagination behavior, but for a read-only search tool the disclosed scope is strong.

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 sentences with no filler: the main action and resource are front-loaded, the output shape is stated, and the boundary with get_card_facts is placed at the end. Every sentence 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 10 optional parameters, a rich schema, and no output schema, the description conveys the essential context: one-line result rows, a pointer to the full-record sibling, and explicit exclusions. Minor gaps remain around default ordering and pagination, but the tool is fundamentally a filtered lookup and the description covers the call-level decisions an agent needs.

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%, so the baseline is 3 and the description does not need to re-document parameters. It names several filter dimensions (issuer, annual fee, network, rewards currency, benefit) but adds no new semantic details beyond the schema, and it omits some parameter categories like lounge access and free-night certificates.

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?

Starts with a specific verb and resource: 'Find credit cards open to new applicants' and enumerates filter dimensions. It distinguishes itself from get_card_facts by noting that it returns only a short row per card, so an agent can tell the two apart immediately.

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 explicit routing guidance: 'call get_card_facts for one card's full record.' The closing sentence states clear exclusions ('no earning rates, welcome-offer amounts, transfer ratios, or bonus sizes'), telling the agent when this tool is not sufficient.

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

All catalog tools Inspect

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

Need Help?