Skip to main content
Glama
Sign In

SecureLend Underwriting

by ai.securelend
OverviewDiscussionsAdmin

Open second-look offer

open_second_look_offer

Open a consented second-look package onto this workspace. Not a credit decision. A person still decides. Does not approve, send, or wire.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "offerId": "<offerId>"
    },
    "name": "open_second_look_offer"
  }
}

Input Schema

NameRequiredDescriptionDefault
offerIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior4/5

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

Annotations already declare this is a non-read-only, non-destructive mutation, and the description adds important guardrails: 'Not a credit decision. A person still decides. Does not approve, send, or wire.' It does not explain whether the operation is idempotent or what exactly gets created, but the added safety context is meaningful beyond the annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is short and front-loaded with the action. The follow-up safety clarifications are useful, though 'Not a credit decision. A person still decides.' is slightly repetitive.

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?

For a simple one-parameter mutation with annotations and no output schema, the definition covers the safety boundary well but leaves the parameter undocumented and does not explain prerequisites or expected workspace effects. It is minimally adequate but has clear gaps.

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?

There is one required parameter (offerId) with 0% schema description coverage, and the description never mentions it. It provides no guidance on where to obtain offerId, its expected format, or its role in opening the package.

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: 'Open a consented second-look package onto this workspace.' It clearly distinguishes the action from a credit decision or approval, but does not explicitly differentiate it from sibling tools such as list_second_look_inbox or open_case.

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 implies that consent must already exist ('consented second-look package') but does not explain when to use this tool versus alternatives like list_second_look_inbox. No prerequisites or exclusions are stated.

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

All SecureLend Underwriting 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