SecureLend Market

Compare savings accounts

compare_savings_accounts

Read-only

List savings account 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: -{
-  "initialDeposit": {
-    "description": "The initial deposit amount in USD.",
-    "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"
-          },
-          "imageUrl": {
-            "type": "string"
-          },
-          "interestRate": {
-            "type": "string"
-          },
-          "issuer": {
-            "type": "string"
-          },
-          "minBalanceForApy": {
-            "type": "string"
-          },
-          "monthlyFee": {
-            "type": "string"
-          },
-          "name": {
-            "type": "string"
-          },
-          "rating": {
-            "maximum": 5,
-            "minimum": 0,
-            "type": "number"
-          }
-        },
-        "required": [
-          "accountId",
-          "name",
-          "issuer",
-          "imageUrl",
-          "rating",
-          "apy",
-          "minBalanceForApy",
-          "monthlyFee"
-        ],
-        "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, destructiveHint=false and openWorldHint=false; the description's one contributing fact is that results come from the internal SecureLend catalog, which reinforces the closed-world hint. It does not say what a result record contains (rates, fees, terms) or whether all accounts are returned in one call, which matters since there is no output schema.

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, purpose front-loaded, zero filler. Nothing could be removed without losing information.

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 carries the burden of describing return values, yet it only says 'list options' — no indication of the fields (interest rate, minimum balance, fees) or result count. For a simple no-arg tool this is workable but leaves the agent guessing what comes back.

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?

Zero parameters, so the baseline is 4. The sentence 'This tool takes no inputs' is redundant with the empty schema but confirms the agent cannot filter or page, which is mildly useful.

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 ('List') and resource ('savings account options from the SecureLend catalog'), and the product noun implicitly separates it from the many other compare_* siblings covering loans, mortgages and credit cards. It does not explicitly name an alternative, so it stops short of a 5.

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?

Usage is only implied by the product name; there is no statement of when to pick this over compare_personal_banking or compare_business_banking, and no prerequisites or exclusions. Adequate for an obvious zero-input catalog lookup, but nothing routes the agent explicitly.

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?