Skip to main content
Glama

Credit Guru

Find credit cards

find_cards
Read-onlyIdempotent

Filter the Credit Guru card catalog by type, annual fee, credit level and foreign fee. Returns issuer facts, our rating and review links, best rated first.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "find_cards"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeNo
limitNo
queryNoPart of a card or issuer name, e.g. "sapphire".
audienceNoPersonal (default) or small business cards.
credit_levelNoOnly cards aimed at this credit level or below.
max_annual_feeNo
no_foreign_feeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds information annotations cannot: the return content (issuer facts, rating, review links) and the deterministic sort order "best rated first", which affects how an agent should interpret results.

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, with the action and filter dimensions front-loaded and return behavior following. Every clause carries distinct information.

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

Completeness3/5

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

For a 7-parameter, zero-required tool with no output schema, the description tells the agent what comes back and in what order, which is valuable. But it omits default behavior when no filters are supplied and silently leaves limit, query and audience unexplained, which matters since the tool is unpaginated in the description.

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 only 43%, so the description must compensate, and it covers type, max_annual_fee, credit_level and no_foreign_fee by name. It says nothing about limit, query or audience, leaving three parameters' intent to the bare schema (and limit has no description at all).

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb+resource: "Filter the Credit Guru card catalog" and names the filter dimensions (type, annual fee, credit level, foreign fee). This distinguishes it from a single-card fetch or a curated best-of list, though it never names sibling tools like get_best_cards or get_card explicitly.

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 filtering framing and the enumerated criteria, so an agent can infer this is the browse/search entry point. However, there is no explicit when-to-use versus get_best_cards or get_card, and no statement about what happens when all filters are omitted (full catalog dump vs error).

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