Skip to main content
Glama

List credit cards

crunch_list_credit_cards
Read-only

List a business's credit cards with balances, default flags, and unmatched statement entries to review card accounts and identify statement items needing reconciliation.

Instructions

List the business's credit cards with their balances, default flag and unmatched statement entries.

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": "crunch_list_credit_cards"
  }
}

Input Schema

NameRequiredDescriptionDefault
rawNoReturn the full objects from the API instead of compact summaries (larger)
limitNoMaximum number of items
fieldsNoKeep only these fields (dot paths, such as supplier.companyName)
searchNoCase-insensitive substring match on any value
statusNoWhich to list: active (default), archived or all

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 useful return-content context ('balances, default flag and unmatched statement entries') but says nothing about ordering, pagination despite a limit parameter, or the default active-only filtering behavior.

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 sentence with the resource and its returned fields front-loaded; no filler, no redundancy.

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?

This is a simple read-only list tool with fully documented parameters and no output schema, and the description sketches the return contents. The only shortfall is the absence of any note on filtering or result limits, which matters given the limit and status parameters.

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 every parameter including the status enum and its active default is already documented in the schema. The description adds no parameter-level meaning beyond that, so the baseline of 3 is appropriate.

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 names a specific verb and resource ('List the business's credit cards') and specifies the payload ('balances, default flag and unmatched statement entries'), which distinguishes it from the singular crunch_get_credit_card. It stops short of naming an alternative explicitly, but the resource scope is unambiguous.

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 rather than stated: an agent can infer this is the collection-level listing versus crunch_get_credit_card for a single record, but the description never says so, nor does it mention pagination or how to narrow results with the status/search parameters.

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