Skip to main content
Glama
Sign In

SecureLend Underwriting

by ai.securelend
OverviewDiscussionsAdmin

List originator leads

list_originator_leads
Read-only

List ranked originator submissions for this workspace. Complete packs with zero knockouts first. Knockout labels are desk-only. This is not a credit decision. Does not open, send, or approve. A person still decides.

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": "list_originator_leads"
  }
}

Input Schema

NameRequiredDescriptionDefault
sinceNoISO timestamp. Omit to include every lead.
completeNotrue = found===required and zero knockouts. false = the rest.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior4/5

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

Beyond the read-only, closed-world, non-destructive annotations, it discloses the prioritization behavior, the desk-only sensitivity of knockout labels, and the requirement for human decision-making. The specific exclusions for opening, sending, and approving further clarify operational boundaries, although return and pagination behavior remain unstated.

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 compact and front-loaded with the operation and workspace scope. Its short sentences efficiently add ordering, confidentiality, side-effect, and human-decision boundaries without filler.

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 two-parameter read-only listing tool, the combined description and schema provide enough scope, filtering, ordering, and safety context to invoke it correctly. With no output schema, the absence of returned-field or pagination details is a minor gap, and an explicit pointer to open_originator_lead for follow-up would improve end-to-end guidance.

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?

Schema description coverage is 100%, so both since and complete are already documented, including the precise meaning of complete=true and complete=false. The description’s complete-pack wording reinforces the domain context but adds no substantial parameter syntax, filtering interaction, or usage detail beyond the schema.

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?

“List ranked originator submissions for this workspace” supplies a specific verb, resource, and scope, while “Complete packs with zero knockouts first” defines the ranking. “Does not open, send, or approve” also helps distinguish it from siblings such as open_originator_lead and action-oriented tools.

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?

The description establishes a clear review-and-prioritization context and explicitly excludes opening, sending, approving, and making credit decisions. It does not name the appropriate sibling for opening a lead or performing those other actions, so the routing guidance is not fully explicit.

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