Skip to main content
Glama
Sign In

LunaTerminal

by com.lunaterminal
OverviewDiscussionsAdmin

Client email triage

triage_email
Read-onlyIdempotent

Classify the text of an incoming client email and detect fraud red flags such as new banking details or requests to avoid a phone call. Returns the risk level, urgency, complaint logging flag, and suggested steps for the advisor, including verification by phone when fraud or account takeover is suspected.

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": {
      "text": "<text>"
    },
    "name": "triage_email"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYesThe email text (subject and body), up to 20,000 characters.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

The annotations already establish that this is a read-only, idempotent, non-destructive, closed-world operation. The description adds meaningful behavioral context by enumerating returned fields (risk level, urgency, complaint logging flag, suggested steps) and explaining that phone verification is suggested when fraud or account takeover is suspected.

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 two tightly written sentences. The core action and fraud context are front-loaded, followed by the return values, with no unnecessary wording.

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?

For a simple one-parameter tool with strong annotations and no output schema, the description is complete enough to call correctly. It compensates for the missing output schema by summarizing the returned risk, urgency, complaint flag, and suggested steps.

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?

With schema description coverage at 100%, the schema already documents the single 'text' parameter and its 20,000 character limit. The description adds only a high-level restatement ('text of an incoming client email') and no additional formatting or parsing semantics 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?

The description uses specific verbs ('Classify', 'detect') on a clear resource ('incoming client email') and names concrete fraud red flags such as new banking details or avoiding a phone call. It also lists the outputs, making it easy to distinguish from the finance-oriented sibling 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 intended scenario is clear: triaging incoming client email text, especially for fraud red flags. It gives useful examples of what to look for, but it does not explicitly state when not to use it or name an alternative such as compliance_screen.

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

All LunaTerminal 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