Skip to main content
Glama

Credit Guru

Get card details

get_card
Read-onlyIdempotent

Full facts for one card by slug: fees, rewards, APRs, welcome offer, our rating breakdown, pros and cons, and the issuer source.

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": {
      "slug": "<slug>"
    },
    "name": "get_card"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesCard slug from find_cards, e.g. "citi-double-cash".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is fully covered without prose. The description's added value is enumerating what content comes back (fees, APRs, rating breakdown, pros/cons, issuer source), which is genuinely useful given there is no output schema, but it says nothing about missing-slug errors or data freshness.

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?

A single front-loaded sentence that leads with scope ('Full facts for one card by slug') and then spends the remainder on the returned payload; no filler or repetition.

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?

For a single-parameter read lookup whose annotations carry the safety profile, the definition covers the essentials and compensates for the absent output schema by listing returned content. It leaves only minor gaps, such as behavior when the slug is unknown.

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?

With one parameter and 100% schema description coverage, the schema already explains the slug and even points to find_cards as its source. The description's 'one card by slug' adds no syntax, format, or validation meaning beyond that, so baseline 3 applies.

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 states a specific verb-plus-resource — returning full facts for one card identified by slug — and enumerates the fields returned (fees, rewards, APRs, welcome offer, rating breakdown, pros/cons, issuer source). It is clearly distinct from find_cards or get_best_cards in character, though it never names a sibling to sharpen the contrast.

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 only implied: 'by slug' hints that this is a follow-up lookup after find_cards, but the description never says when to choose this over get_best_cards or list_current_offers, nor any prerequisites or when-not-to-use conditions.

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