Skip to main content
Glama

minia2a — hosted x402 API marketplace (HTTP)

x402-is-credit-card

Is Credit Card: Checks whether a digit string passes the Luhn checksum and returns a boolean 🆓 5 free trial calls per signed wallet

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": "x402-is-credit-card"
  }
}

Input Schema

NameRequiredDescriptionDefault
inputNo
valueNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • removedInput schema / properties / input / description
      Removed value: -"Input to process"
    • removedInput schema / properties / value / description
      Removed value: -"Value to process"
  2. First observed

TDQS

C2.9/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It usefully discloses the underlying algorithm (Luhn checksum) and that the result is a boolean, which is meaningful because it signals a checksum-only check rather than issuer/card-type validation. However, it says nothing about invalid-input handling, error behavior, or what 'value' vs 'input' do.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One front-loaded sentence states the operation and return type with no wasted prose. The trailing pricing badge adds marketing noise but does not obscure the core statement.

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

Completeness2/5

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

No output schema, no annotations, and two undocumented parameters leave key calling details unaddressed. The boolean return is covered, but the schema ambiguity and absence of any when-to-use context make the definition incomplete for reliable invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Two parameters exist with 0% schema description coverage, so the description must compensate. It mentions a 'digit string' but never maps that to the ambiguous 'input' or 'value' fields, leaving the agent guessing which argument to populate.

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 (checks) and a concrete operation (Luhn checksum on a digit string) plus the return type (boolean). It stops short of distinguishing itself from near-identical siblings such as x402-is-luhn and x402-credit-card-validate, and the name 'is-credit-card' overstates what is really only a checksum test.

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 guidance on when to use this versus the many sibling validators (x402-is-credit-card-valid, x402-credit-card-validate, x402-credit-card-type, x402-is-luhn). The only added clause concerns free trial calls, which is billing information rather than usage context.

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.