SecureLend Market

Compare personal banking

compare_personal_banking

Read-only

List personal checking 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: -{
-  "features": {
-    "description": "Desired account features.",
-    "items": {
-      "type": "string"
-    },
-    "type": "array"
-  }
-}

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": {
-          "accountId": {
-            "type": "string"
-          },
-          "apy": {
-            "type": "string"
-          },
-          "bestFor": {
-            "type": "string"
-          },
-          "bonus": {
-            "type": "string"
-          },
-          "imageUrl": {
-            "type": "string"
-          },
-          "interestRate": {
-            "type": "string"
-          },
-          "issuer": {
-            "type": "string"
-          },
-          "monthlyFee": {
-            "type": "string"
-          },
-          "name": {
-            "type": "string"
-          },
-          "overdraftRating": {
-            "maximum": 5,
-            "minimum": 0,
-            "type": "number"
-          },
-          "rating": {
-            "maximum": 5,
-            "minimum": 0,
-            "type": "number"
-          }
-        },
-        "required": [
-          "accountId",
-          "name",
-          "issuer",
-          "imageUrl",
-          "rating",
-          "bestFor",
-          "apy",
-          "bonus",
-          "monthlyFee",
-          "overdraftRating"
-        ],
-        "type": "object"
-      },
-      "type": "array"
-    }
-  },
-  "required": [
-    "offers",
-    "metadata"
-  ],
-  "type": "object"
-}New value: +null

First observedMay 27, 2026

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, openWorldHint=false, and destructiveHint=false, so the safety profile is covered. The description adds that results come from the SecureLend catalog and that no inputs are required, but does not describe return fields, pagination, or catalog 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?

Two short sentences, front-loaded with the purpose and followed by the relevant no-input constraint. There is 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?

For a zero-parameter read-only listing tool, annotations and schema cover much of the context. However, with no output schema, the description could say more about what a 'personal checking option' includes or what the list returns.

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 for parameter semantics is 4. The description confirms 'This tool takes no inputs,' which is consistent with the empty input schema.

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 states a specific verb and resource: list personal checking options from the SecureLend catalog. It is clear enough to distinguish this from siblings like compare_savings_accounts and compare_business_banking, though it does not explicitly name alternatives.

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 intended use is implied by 'List personal checking options,' and the tool's zero-input nature is stated. However, the description does not explain when to choose this over sibling comparison tools or mention any exclusions.

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?