Skip to main content
Glama

SecureLend Market

by ai.securelend.mcp
OverviewDiscussionsAdmin

display_upload_documents_form

Display a form that lets users upload supporting documents for an existing application.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 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": "Pre-fill the application ID for the document upload form.",
-    "type": "string"
-  }
-}
    • changedOutput schema / (root)
      Previous value: -{
-  "$schema": "http://json-schema.org/draft-07/schema#",
-  "additionalProperties": false,
-  "properties": {},
-  "type": "object"
-}New value: +null
  2. First observed

TDQS

A3.5/5.0
Behavior3/5

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

There are no annotations, so the description must carry the behavioral burden. The verb 'display' implies a non-mutating UI action, which is helpful, but the description does not state whether the form actually submits documents, whether side effects occur, or how this relates to submit_documents. It is minimally transparent but not rich.

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?

A single sentence that is direct and free of redundant wording. It front-loads the action ('Display a form') and packs the key context ('upload supporting documents', 'existing application') into a compact, readable definition.

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

Completeness4/5

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

For a simple zero-parameter display tool, the description is largely complete: it says what UI to show and for what purpose. It could add a note that document submission is handled separately (e.g., by submit_documents), but this is a minor gap rather than a blocking omission.

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?

The tool has zero parameters and 100% schema description coverage, so there is nothing for the description to clarify about inputs. The baseline of 4 applies because parameter semantics are effectively moot, and the description correctly says nothing misleading.

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 a specific verb ('display') and resource ('a form that lets users upload supporting documents for an existing application'), which clearly distinguishes it from form tools for other purposes like display_offer_form or display_prequalification_form. It does not explicitly call out sibling differentiation, but the purpose is unambiguous.

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 about when to use this tool versus alternatives. The phrase 'for an existing application' provides a slight contextual hint, but there is no mention of exclusions, prerequisites, or why an agent should choose this over submit_documents or the other display_* tools.

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