Skip to main content
Glama
Sign In

SecureLend Underwriting

by ai.securelend
OverviewDiscussionsAdmin

Sign funding batch

sign_funding_batch

Named human signs a ready funding batch into purchases after confirmed true. Funded stays false. Live sign already registers blind-registry tokens. Does not close 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": {
      "caseId": "<caseId>",
      "batchId": "<batchId>"
    },
    "name": "sign_funding_batch"
  }
}

Input Schema

NameRequiredDescriptionDefault
caseIdYes
batchIdYes
confirmedNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.3/5.0
Behavior4/5

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

Annotations declare a non-read-only, non-destructive, closed-world mutation, and the description adds genuinely non-obvious behavior on top: 'Funded stays false', the live-sign blind-registry token registration, and the fact that it neither closes the case nor wires funds. It also implies a human-authorization requirement via 'Named human signs'. The only deduction is that the phrasing is compressed enough to be ambiguous about what 'Funded stays false' actually protects.

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?

Four short sentences, front-loaded with the action, and every sentence carries information. The telegraphic fragments ('Funded stays false', 'into purchases') trade clarity for brevity and can be parsed more than one way.

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 mutation with no output schema and zero schema coverage, the description covers side effects, scope boundaries, and the human-signer requirement reasonably well. It stops short of explaining the two required identifiers or what a successful sign returns, which an agent needs before invoking.

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?

Schema description coverage is 0%, so the description carries the full burden for three parameters, and it only indirectly explains 'confirmed' through 'after confirmed true'. Neither caseId nor batchId is mentioned at all, leaving the agent to infer which identifiers are required and what they scope.

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?

States a specific verb and resource: a named human 'signs a ready funding batch into purchases', and the closing clause 'Does not close or wire' separates it from siblings like close_case_to_loan and register_financed_invoice. The jargon ('into purchases', 'blind-registry tokens') is not standard enough for a clean 5, but the operation is identifiable.

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?

'after confirmed true' supplies a real precondition, and 'Does not close or wire' supplies an exclusion. What's missing is any named alternative for the cases it excludes, or context on when a batch is 'ready' versus still being assembled.

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