SecureLend Market

Compare personal credit cards

compare_personal_credit_cards

Read-only

List personal credit card options from the SecureLend catalog. This tool takes no inputs.

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed7 schema fields changedOct 26, 2026

removedInput schema / properties / amount

Removed value: -{
-  "description": "Requested amount.",
-  "type": "number"
-}

removedInput schema / properties / creditScore

Removed value: -{
-  "description": "Credit score used to filter options.",
-  "type": "number"
-}

removedInput schema / properties / homePrice

Removed value: -{
-  "description": "Property value for a mortgage comparison.",
-  "type": "number"
-}

removedInput schema / properties / loanAmount

Removed value: -{
-  "description": "Requested amount.",
-  "type": "number"
-}

removedInput schema / properties / principal

Removed value: -{
-  "description": "Principal when loanAmount is omitted.",
-  "type": "number"
-}

removedInput schema / properties / purpose

Removed value: -{
-  "description": "What the amount is for.",
-  "type": "string"
-}

removedInput schema / properties / state

Removed value: -{
-  "description": "US state.",
-  "type": "string"
-}

Changed2 schema fields changedOct 23, 2026

changedInput schema / additionalProperties
```
Previous value: -trueNew value: +false
```

addedInput schema / properties

Added value: +{
+  "amount": {
+    "description": "Requested amount.",
+    "type": "number"
+  },
+  "creditScore": {
+    "description": "Credit score used to filter options.",
+    "type": "number"
+  },
+  "homePrice": {
+    "description": "Property value for a mortgage comparison.",
+    "type": "number"
+  },
+  "loanAmount": {
+    "description": "Requested amount.",
+    "type": "number"
+  },
+  "principal": {
+    "description": "Principal when loanAmount is omitted.",
+    "type": "number"
+  },
+  "purpose": {
+    "description": "What the amount is for.",
+    "type": "string"
+  },
+  "state": {
+    "description": "US state.",
+    "type": "string"
+  }
+}

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: -{
-  "creditScore": {
-    "description": "The applicant's estimated credit score (300-850).",
-    "maximum": 850,
-    "minimum": 300,
-    "type": "number"
-  },
-  "rewardsType": {
-    "description": "Preferred rewards type.",
-    "enum": [
-      "cash_back",
-      "travel",
-      "points"
-    ],
-    "type": "string"
-  }
-}

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": {
-          "bestFor": {
-            "type": "string"
-          },
-          "cardId": {
-            "type": "string"
-          },
-          "imageUrl": {
-            "type": "string"
-          },
-          "introOffer": {
-            "type": "string"
-          },
-          "issuer": {
-            "type": "string"
-          },
-          "name": {
-            "type": "string"
-          },
-          "rating": {
-            "maximum": 5,
-            "minimum": 0,
-            "type": "number"
-          },
-          "recommendedCreditScore": {
-            "type": "string"
-          },
-          "rewardsRate": {
-            "type": "string"
-          },
-          "terms": {
-            "additionalProperties": false,
-            "properties": {
-              "apr": {
-                "additionalProperties": false,
-                "properties": {
-                  "balanceTransfer": {
-                    "type": "number"
-                  },
-                  "penalty": {
-                    "type": "number"
-                  },
-                  "purchase": {
-                    "type": "number"
-                  }
-                },
-                "required": [
-                  "purchase",
-                  "balanceTransfer"
-                ],
-                "type": "object"
-              },
-              "fees": {
-                "additionalProperties": false,
-                "properties": {
-                  "annual": {
-                    "type": "number"
-                  }
-                },
-                "required": [
-                  "annual"
-                ],
-                "type": "object"
-              }
-            },
-            "required": [
-              "apr",
-              "fees"
-            ],
-            "type": "object"
-          }
-        },
-        "required": [
-          "cardId",
-          "name",
-          "issuer",
-          "imageUrl",
-          "rating",
-          "bestFor",
-          "rewardsRate",
-          "introOffer",
-          "recommendedCreditScore",
-          "terms"
-        ],
-        "type": "object"
-      },
-      "type": "array"
-    }
-  },
-  "required": [
-    "offers",
-    "metadata"
-  ],
-  "type": "object"
-}New value: +null

First observedMay 27, 2026

TDQS

A3.5/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, openWorldHint=false, and 'from the SecureLend catalog' usefully reinforces the closed-world scope. Beyond that the description adds little: it does not say what the list contains (rates, fees, eligibility), whether results are ranked or limited, or what a caller learns from the response.

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?

Two short sentences with the resource stated first, so the definition is front-loaded and cheap to read. The second sentence restates what the empty input schema already proves, which is minor waste.

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?

For a no-arg read tool with a closed-world annotation and no output schema, the description is callable as written. The gap is the return value: with no output schema, the description is the only place to say what a 'credit card option' record includes, and it does not.

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?

There are zero parameters, so the baseline is 4. The sentence 'This tool takes no inputs' is consistent with the empty schema but is largely redundant with it rather than adding new meaning.

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?

States a specific verb+resource ('List personal credit card options') and names the source catalog (SecureLend), which is enough to separate it from compare_business_credit_cards and compare_personal_loans without opening a schema. It stops short of explicitly naming the sibling it excludes, so it is clear but not maximally differentiated.

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?

'List ... options' plus 'takes no inputs' implies a browsing/comparison use case, and the parallel naming family makes the choice fairly self-evident. However, there is no explicit when-to-use or when-not-to-use statement, no mention of when to prefer compare_business_credit_cards, and no note on whether a follow-up like create_lender_enquiry is expected.

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?