Skip to main content
Glama

SecureLend Market

by ai.securelend.mcp
OverviewDiscussionsAdmin

submit_documents

Generate a presigned upload URL and create document metadata for an application in SecureLend storage.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • 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 ID of the application to associate the document with.",
-    "type": "string"
-  },
-  "documentType": {
-    "description": "The category of the document.",
-    "enum": [
-      "articles-of-incorporation",
-      "balance-sheet",
-      "bank-statement",
-      "business-license",
-      "business-plan",
-      "contract",
-      "drivers-license",
-      "financial-statement",
-      "identity-document",
-      "invoice",
-      "lease-agreement",
-      "other-business-document",
-      "other-personal-document",
-      "passport",
-      "profit-and-loss-statement",
-      "proof-of-address",
-      "proof-of-income",
-      "property-document",
-      "purchase-order",
-      "tax-return",
-      "utility-bill",
-      "vehicle-document",
-      "voided-check"
-    ],
-    "type": "string"
-  },
-  "fileName": {
-    "description": "The original name of the file.",
-    "type": "string"
-  }
-}
    • removedInput schema / required
      Removed value: -[
-  "applicationId",
-  "fileName",
-  "documentType"
-]
    • changedOutput schema / (root)
      Previous value: -{
-  "$schema": "http://json-schema.org/draft-07/schema#",
-  "additionalProperties": false,
-  "properties": {
-    "documentId": {
-      "type": "string"
-    },
-    "message": {
-      "type": "string"
-    },
-    "success": {
-      "type": "boolean"
-    },
-    "uploadFields": {
-      "additionalProperties": {
-        "type": "string"
-      },
-      "propertyNames": {
-        "type": "string"
-      },
-      "type": "object"
-    },
-    "uploadUrl": {
-      "type": "string"
-    }
-  },
-  "required": [
-    "success",
-    "message"
-  ],
-  "type": "object"
-}New value: +null
  2. First observed

TDQS

C2.8/5.0
Behavior2/5

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

No annotations are present, so the description carries the full burden of disclosing side effects and behavior. It mentions generating a presigned URL and creating metadata, implying a write/upload flow, but it does not state whether the actual file upload is part of this call, what happens on failure, what permissions are required, or what response is returned.

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 sentence with no filler. The two key actions are front-loaded and immediately readable.

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?

For a tool with no annotations, no output schema, and an unconstrained input schema, this one-sentence description is insufficient. An agent cannot determine required inputs, response shape, upload mechanics, or error behavior from the provided definition.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema declares no named parameters and allows arbitrary additional properties, making the description the only source of invocation guidance. It does not specify an application ID, file names, metadata keys, or any required arguments, so an agent cannot construct a correct call from the definition alone.

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 names concrete operations ('generate a presigned upload URL', 'create document metadata') and a resource scope ('an application in SecureLend storage'). This is specific enough to separate the backend submission action from the sibling display_upload_documents_form, though it does not explicitly name any sibling.

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?

No guidance is given on when to invoke this tool or when to prefer alternatives such as display_upload_documents_form or track_offer_status. There are no preconditions, ordering notes, or exclusions, so an agent must infer usage entirely from the name and one-line description.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All SecureLend Market toolsInspect
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