LendMail

Analyze mail piece (deprecated compatibility alias)

analyze_mail_piece

Analyze a photo of a mailed credit card offer, prescreened credit offer, personal loan offer, or other loan solicitation. Deprecated compatibility alias for start_mail_analysis. Prefer start_mail_analysis. Accepts optional image_url or image_base64 from older clients but ignores them and never fetches, decodes, stores, or logs image data. Returns a session link the user opens to upload the photo on LendMail, then call get_mail_analysis with the session_id.

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

Input Schema

Name	Required	Description	Default
`image_url`	No	Ignored. Images are not accepted over MCP; use the returned session_url instead.
`image_base64`	No	Ignored. Images are not accepted over MCP; use the returned session_url instead.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 10, 2026

TDQS

A4.7/5.0

Behavior4/5

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

Beyond the annotations (readOnlyHint=false, idempotentHint=false, which fit a session-creating write), the description discloses that image data is never fetched, decoded, stored, or logged, and that a session link is returned for user-side upload. That is substantive behavioral context. Minor gap: it doesn't say whether repeated calls create duplicate sessions.

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 front-loaded with the deprecated-alias warning and the preferred alternative, then the parameter caveat, then the return/workflow. Every sentence carries distinct information and nothing is repeated from structured fields verbatim.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description fully explains the return value (a session link) and the required next step. For a two-parameter, zero-required compatibility shim, nothing an agent needs to invoke it correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and the schema already says both parameters are 'Ignored'. The description adds meaning beyond the schema by explaining the reason (images are not accepted over MCP) and guaranteeing no fetch/decode/store/log, which is a stronger contract than 'Ignored' alone.

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?

States a specific verb and resource ('Analyze a photo of a mailed credit card offer... loan solicitation') and immediately labels itself a deprecated compatibility alias for start_mail_analysis. An agent can distinguish this from its siblings without opening any schema.

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

Usage Guidelines5/5

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

Explicitly routes the agent: 'Prefer start_mail_analysis', and spells out the downstream workflow ('Returns a session link the user opens... then call get_mail_analysis with the session_id'). Both the alternative and the follow-up call are named with their conditions.

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

All LendMail tools Inspect

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

Need Help?