Skip to main content
Glama

Upload offer documents

upload_offer_documents

Create a presigned upload URL and document metadata for an existing SecureLend enquiry. The file is stored on that enquiry. This does not submit a credit decision.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "upload_offer_documents"
  }
}

Input Schema

NameRequiredDescriptionDefault
idNo
xmlNo
contentNo
fileNameNo
mimeTypeNo
enquiryIdNo
contentTypeNo
documentTypeNo
applicationIdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / properties / content
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / contentType
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / mimeType
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / xml
      Added value: +{
      +  "type": "string"
      +}
  2. Added

TDQS

A3.6/5.0
Behavior4/5

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

Beyond the non-read-only, non-destructive annotations, it discloses that a presigned URL and metadata are created, that the file is stored on the enquiry, and that no credit decision is triggered. It omits operational details such as URL expiry, whether a separate upload request is required, and overwrite or idempotency behavior.

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?

Three short sentences are front-loaded with the action and resource, then add the storage scope and a valuable non-goal. There is no filler or repetition.

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?

The core purpose and non-goal are covered, but the definition is insufficient for reliably invoking a nine-parameter mutation with no required fields and no output schema. The missing parameter contract and presigned-upload workflow are substantial gaps, although the description at least identifies the expected URL and metadata result.

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?

With nine parameters at 0% schema description coverage, the description only broadly implies an enquiry identifier and document content or metadata. It does not disambiguate id, enquiryId, and applicationId; xml and content; or mimeType and contentType, nor does it provide required combinations, formats, or allowed documentType values.

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 uses a specific verb and resource—“Create a presigned upload URL and document metadata”—and scopes the operation to an existing SecureLend enquiry. Its function is clear, but it does not explicitly distinguish itself from display_upload_documents_form or the enquiry and offer siblings.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Requiring an existing enquiry supplies a useful precondition, and “This does not submit a credit decision” establishes an explicit when-not boundary. It does not say when to use this flow rather than display_upload_documents_form, nor what must happen after the presigned URL is created.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources