Skip to main content
Glama

Credit Guru

Get a best-of card list

get_best_cards
Read-onlyIdempotent

A ranked Credit Guru best-of list, such as cash back, travel, balance transfer, business or cards for a credit level.

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": {
      "list": "<list>"
    },
    "name": "get_best_cards"
  }
}

Input Schema

NameRequiredDescriptionDefault
listYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already establish read-only, idempotent, non-destructive, closed-world behavior, so the description need not carry safety signaling. It adds that results are ranked and gives category examples, but does not explain ranking order, result size, or pagination.

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?

The definition is one front-loaded sentence with no filler. It is appropriately sized for a simple lookup tool.

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?

The description, enum, and annotations are enough to identify the resource and safety profile, but there is no output schema and no usage routing. Gaps remain around when to choose this tool versus siblings and what the ranked list actually contains.

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?

The single required list parameter has 0% schema description coverage, so the description must carry semantics; its examples explain common categories and imply that 'cards for a credit level' maps to the credit-* enum values. However, it is non-exhaustive and does not document all 14 allowed values or validation rules.

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?

The description identifies a ranked Credit Guru best-of card list and gives representative categories, so an agent can tell it returns curated rankings rather than individual cards or offers. It does not explicitly contrast with find_cards or list_current_offers, so sibling differentiation is incomplete.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no explicit when-to-use or when-not-to-use guidance and no named alternative. The only cue is the implied use of retrieving a best-of list by category, leaving the agent to infer when this is preferable to find_cards or list_current_offers.

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