SecureLend Market

Compare business banking

compare_business_banking

Read-only

List business checking options from the SecureLend catalog. The only optional input is maxResults, which limits how many rows are returned.

Input Schema

Name	Required	Description	Default
`maxResults`	No	Maximum number of checking rows to return. Optional.

Schema Changelog

Changes observed during successful MCP inspections.

Changed8 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"
-}

addedInput schema / properties / maxResults

Added value: +{
+  "description": "Maximum number of checking rows to return. Optional.",
+  "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: -{
-  "industry": {
-    "description": "The business's industry.",
-    "type": "string"
-  },
-  "monthlyTransactions": {
-    "description": "Estimated number of monthly transactions.",
-    "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": {
-          "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"
-          },
-          "rating": {
-            "maximum": 5,
-            "minimum": 0,
-            "type": "number"
-          }
-        },
-        "required": [
-          "accountId",
-          "name",
-          "issuer",
-          "imageUrl",
-          "rating",
-          "bestFor",
-          "apy",
-          "monthlyFee",
-          "bonus"
-        ],
-        "type": "object"
-      },
-      "type": "array"
-    }
-  },
-  "required": [
-    "offers",
-    "metadata"
-  ],
-  "type": "object"
-}New value: +null

First observedMay 27, 2026

TDQS

B3.2/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 safety is covered. The description adds that options come from a bounded 'SecureLend catalog' and that maxResults caps rows, but says nothing about what a 'checking row' contains, ordering, or whether results include rates/fees.

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, front-loaded sentences with no padding. The second sentence is somewhat redundant with the schema, slightly reducing value per word.

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?

With no output schema, the description would benefit from stating what the returned rows include (product names, rates, fees) since that is exactly the information an agent comparing options needs. As written, it is functional but leaves the return shape unspecified.

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% for the single optional maxResults parameter, so the schema already carries the full semantics. The description merely restates it ('the only optional input is maxResults, which limits how many rows are returned') without adding default or limit-range information.

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 and resource — 'List business checking options from the SecureLend catalog' — which is concrete enough to distinguish it from sibling products like credit cards or mortgages. However, the name promises 'compare' while the description only says 'list', and no sibling is named as an explicit alternative.

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 statement of when to use this tool versus the many sibling compare_* tools, nor any prerequisites or exclusions. The agent must infer from the product name alone that this covers business checking accounts and not, say, savings or loans.

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?