SecureLend Market

track_offer_status

Retrieve the status of previously submitted SecureLend enquiries by application ID or applicant email.

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 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: -{
-  "applicationId": {
-    "description": "The unique ID of the application to track.",
-    "type": "string"
-  }
-}

removedInput schema / required
```
Removed value: -[
-  "applicationId"
-]
```

changedOutput schema / (root)

Previous value: -{
-  "$schema": "http://json-schema.org/draft-07/schema#",
-  "additionalProperties": false,
-  "properties": {
-    "applications": {
-      "items": {
-        "additionalProperties": false,
-        "properties": {
-          "applicationId": {
-            "description": "Alias of `id`. Pass this value as `applicationId` to the `track_offer_status` tool to check enquiry status later.",
-            "type": "string"
-          },
-          "createdAt": {
-            "description": "The timestamp when the application was created.",
-            "type": "string"
-          },
-          "id": {
-            "description": "The unique ID of the application.",
-            "type": "string"
-          },
-          "productType": {
-            "anyOf": [
-              {
-                "enum": [
-                  "INSTALLMENT_LOAN",
-                  "LINE_OF_CREDIT",
-                  "SHORT_TERM_CREDIT",
-                  "BNPL",
-                  "MORTGAGE",
-                  "AUTO_LOAN",
-                  "AUTO_REFINANCE",
-                  "STUDENT_LOAN",
-                  "STUDENT_LOAN_REFINANCE",
-                  "BUSINESS_LOAN",
-                  "BUSINESS_BANKING",
-                  "BUSINESS_CREDIT_CARD",
-                  "PERSONAL_BANKING",
-                  "SAVINGS_ACCOUNT",
-                  "PERSONAL_CREDIT_CARD"
-                ],
-                "type": "string"
-              },
-              {
-                "type": "string"
-              }
-            ],
-            "description": "The type of product applied for."
-          },
-          "providers": {
-            "description": "The list of providers the application was sent to.",
-            "items": {
-              "additionalProperties": false,
-              "properties": {
-                "error": {
-                  "type": "string"
-                },
-                "providerApplicationId": {
-                  "type": "string"
-                },
-                "providerId": {
-                  "type": "string"
-                },
-                "providerName": {
-                  "type": "string"
-                },
-                "referralUrl": {
-                  "format": "uri",
-                  "type": "string"
-                },
-                "status": {
-                  "enum": [
-                    "PENDING",
-                    "SUBMITTED",
-                    "REFERRED",
-                    "ERROR",
-                    "RECEIVED"
-                  ],
-                  "type": "string"
-                },
-                "submittedAt": {
-                  "type": "string"
-                }
-              },
-              "required": [
-                "providerId",
-                "providerName",
-                "status"
-              ],
-              "type": "object"
-            },
-            "type": "array"
-          },
-          "requiredInfo": {
-            "additionalProperties": false,
-            "description": "Details on information required from the applicant when status is ACTION_REQUIRED.",
-            "properties": {
-              "documents": {
-                "description": "List of required document types.",
-                "items": {
-                  "type": "string"
-                },
-                "type": "array"
-              },
-              "message": {
-                "type": "string"
-              },
-              "sections": {
-                "description": "List of required additional information sections.",
-                "items": {
-                  "type": "string"
-                },
-                "type": "array"
-              }
-            },
-            "type": "object"
-          },
-          "status": {
-            "description": "The current status of the application.",
-            "enum": [
-              "DRAFT",
-              "SUBMITTED",
-              "IN_REVIEW",
-              "ACTION_REQUIRED",
-              "APPROVED",
-              "DECLINED",
-              "CLOSED"
-            ],
-            "type": "string"
-          }
-        },
-        "required": [
-          "id",
-          "createdAt",
-          "status",
-          "productType",
-          "providers"
-        ],
-        "type": "object"
-      },
-      "type": "array"
-    }
-  },
-  "required": [
-    "applications"
-  ],
-  "type": "object"
-}New value: +null

First observedMay 27, 2026

TDQS

B3.2/5.0

Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only says 'retrieve', which implies a read-only operation, but it does not mention authentication requirements, error handling (e.g., not found), rate limits, or any side effects. The lack of detail is a significant gap for a tool with zero 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?

The description is a single, well-structured sentence that front-loads the core action and includes the key lookup criteria without unnecessary words. It earns its place and is easy to scan.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the lack of output schema, annotations, and a structured input schema, the description must carry substantial explanatory weight. It fails to specify how to pass the lookup keys, what the response contains, or any constraints. An agent would likely need additional information to call this tool correctly, making it incomplete.

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?

The input schema is empty (additionalProperties: true, no properties), so the description is the only source of parameter guidance. It names the two identifiers (application ID or applicant email) but does not specify exact parameter names, formats, or whether they are required or mutually exclusive. This adds some meaning beyond the schema but remains imprecise.

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 verb ('Retrieve') and a resource ('status of previously submitted SecureLend enquiries'), and clarifies the lookup keys (application ID or applicant email). This clearly distinguishes it from siblings like get_offer or get_multiple_offers, which focus on offer details rather than status tracking.

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?

The description does not specify when to use this tool versus alternatives, nor does it mention any exclusions or prerequisites. The context implies it is for tracking after submission, but this is not explicit, leaving the agent to infer usage.

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?