Skip to main content
Glama

Get credit card

crunch_get_credit_card
Read-only

Retrieve a single credit card by ID, including its opening balance, to view complete card details.

Instructions

Get one credit card in full, including its opening balance.

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": {
      "credit_card_id": "<credit_card_id>"
    },
    "name": "crunch_get_credit_card"
  }
}

Input Schema

NameRequiredDescriptionDefault
credit_card_idYesCredit card ID (see crunch_list_credit_cards)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds that the result is 'in full, including its opening balance', which tells the agent what data completeness to expect, but says nothing about not-found behavior or output shape.

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?

One short sentence with the scope and the notable return detail front-loaded; no filler or redundant restatement of the title.

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 simple single-record getter with full schema coverage, no output schema, and read-only annotations, the definition supplies adequate context; only error/not-found semantics and return field detail are absent.

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% and the single parameter already documents that a credit card ID is expected and where to find it. The description adds no syntax, format, or constraint information beyond that baseline.

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 gives a specific verb and resource ('Get one credit card') and scopes it to a single record, which distinguishes it from the sibling list tool crunch_list_credit_cards. It is clear but does not name the sibling 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 only implied: fetching a single card's full details. There is no explicit when-to-use or when-not guidance, though the parameter schema points to crunch_list_credit_cards for discovery of IDs.

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

Deploy Server

Other Tools