Skip to main content
Glama
Sign In

SecureLend Underwriting

by ai.securelend
OverviewDiscussionsAdmin

List marketplace leads

list_marketplace_leads
Read-only

List plugin and placement enquiries visible to this workspace. Completeness is pack types and facts. 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_marketplace_leads"
  }
}

Input Schema

NameRequiredDescriptionDefault
sinceNoISO timestamp. Omit to include every visible enquiry.
completeNotrue = found===required. false = the rest. Knockouts are not a filter.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, and the description's "does not open, send, or approve" and "a person still decides" are consistent with that safety profile. It adds a human-in-the-loop note that goes slightly beyond the annotations. It says nothing about result shape, ordering, or how many enquiries come back, so the behavioral disclosure remains thin.

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

Conciseness3/5

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

The purpose is front-loaded in the first sentence, which is good. The remaining sentences are short fragments, and "Completeness is pack types and facts" reads as an unexplained aside that costs space without conveying clear information.

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?

This is a simple two-parameter read tool with full schema coverage, no output schema, and annotations that already cover the safety profile. The description states scope and boundaries adequately. A brief note on what an enquiry record contains would make it fully complete, but nothing essential is missing for correct invocation.

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 the schema already explains both 'since' and 'complete' (including the found===required semantics), which sets the baseline at 3. The description's "Completeness is pack types and facts" gestures at the 'complete' parameter but is too cryptic to add usable meaning beyond the schema.

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 gives a concrete verb and resource: "List plugin and placement enquiries visible to this workspace." That is enough for an agent to know it is a scoped read of marketplace enquiries. It does not distinguish this tool from the sibling list_originator_leads, so it falls short of a 5.

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

Usage Guidelines3/5

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

Usage is implied by the workspace-scoping phrase and the negative framing ("not a credit decision", "does not open, send, or approve"), which tells the agent this is not an action tool. However, it never says when to pick this over list_originator_leads or any queue-listing sibling, so the agent has no explicit routing rule.

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