SecureLend Market

compare_business_credit_cards

Find business credit cards matching criteria like rewards type, annual fee, and credit score

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedSep 23, 2026

removedInput schema / $schema

Removed value: -"http://json-schema.org/draft-07/schema#"

addedInput schema / additionalProperties
```
Added value: +true
```

removedInput schema / properties

Removed value: -{
-  "annualRevenue": {
-    "description": "The business's annual revenue in USD.",
-    "minimum": 0,
-    "type": "number"
-  },
-  "businessAgeInYears": {
-    "description": "The age of the business in years.",
-    "minimum": 0,
-    "type": "number"
-  },
-  "creditScore": {
-    "description": "The applicant's estimated credit score (300-850).",
-    "maximum": 850,
-    "minimum": 300,
-    "type": "number"
-  }
-}

changedOutput schema / (root)

Previous value: -{
-  "$schema": "http://json-schema.org/draft-07/schema#",
-  "additionalProperties": false,
-  "properties": {
-    "metadata": {
-      "additionalProperties": false,
-      "properties": {
-        "queryId": {
-          "type": "string"
-        },
-        "sessionId": {
-          "type": "string"
-        },
-        "timestamp": {
-          "type": "string"
-        }
-      },
-      "required": [
-        "queryId",
-        "timestamp"
-      ],
-      "type": "object"
-    },
-    "offers": {
-      "items": {
-        "additionalProperties": false,
-        "properties": {
-          "cardId": {
-            "type": "string"
-          },
-          "creditScoreRange": {
-            "type": "string"
-          },
-          "imageUrl": {
-            "type": "string"
-          },
-          "issuer": {
-            "type": "string"
-          },
-          "name": {
-            "type": "string"
-          },
-          "rating": {
-            "maximum": 5,
-            "minimum": 0,
-            "type": "number"
-          },
-          "terms": {
-            "additionalProperties": false,
-            "properties": {
-              "annualFee": {
-                "type": "number"
-              },
-              "apr": {
-                "type": "number"
-              },
-              "creditLimit": {
-                "additionalProperties": false,
-                "properties": {
-                  "amount": {
-                    "type": "number"
-                  },
-                  "currency": {
-                    "const": "USD",
-                    "type": "string"
-                  }
-                },
-                "required": [
-                  "amount",
-                  "currency"
-                ],
-                "type": "object"
-              }
-            },
-            "required": [
-              "apr",
-              "annualFee",
-              "creditLimit"
-            ],
-            "type": "object"
-          },
-          "welcomeBonus": {
-            "type": "string"
-          }
-        },
-        "required": [
-          "cardId",
-          "name",
-          "issuer",
-          "imageUrl",
-          "rating",
-          "creditScoreRange",
-          "welcomeBonus",
-          "terms"
-        ],
-        "type": "object"
-      },
-      "type": "array"
-    }
-  },
-  "required": [
-    "offers",
-    "metadata"
-  ],
-  "type": "object"
-}New value: +null

First observedMay 27, 2026

TDQS

A3.7/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full burden. It only says 'find' matching cards and gives no indication of side effects, whether it performs a live search, whether it returns offers, or any limitations. This is minimal behavioral disclosure for a tool with no annotation coverage.

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 efficiently states the action, resource, and examples of criteria. Every part earns its place with no filler.

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 tool is simple and the schema is permissive, but the description does not explain how criteria should be formatted as input properties or what kind of result set to expect. It is adequate for basic selection but leaves the agent to guess operational details.

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

Parameters4/5

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

The schema has zero documented parameters and simply allows additional properties, so the description's examples (rewards type, annual fee, credit score) provide the main semantic guidance for what the agent might pass. This adds meaningful value beyond the empty schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific action ('Find') on a specific resource ('business credit cards') and lists concrete matching criteria (rewards type, annual fee, credit score). It clearly distinguishes this tool from siblings like compare_personal_credit_cards and compare_business_loans.

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?

The usage context is implied: use this tool when looking for business credit cards by certain criteria. However, there is no explicit guidance on when not to use it, and the description never names alternatives such as compare_personal_credit_cards for personal card comparisons.

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

All SecureLend Market tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?