Skip to main content
Glama

UAI x402 Security Tools

email-vendor-risk-summary

Summarize vendor email risk for compliance claims, subprocessors, retention, DPA language, and breach notifications. (REST equivalent: POST /api/v1/email-vendor-risk-summary, $0.10)

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": {
      "subject": "<subject>",
      "from": "<from>",
      "body": "<body>"
    },
    "name": "email-vendor-risk-summary"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyYesVendor email body
fromYesVendor sender address
subjectYesVendor email subject
vendorNameNoOptional vendor name

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Only a title annotation is present, so the description carries the full burden. It usefully discloses the REST equivalent and the $0.10 cost, which is real behavioral context, but says nothing about whether the email body is sent to a third party, whether any state is retained, or what form the summary takes. For a read-only analysis tool this is acceptable but incomplete.

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

Conciseness4/5

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

Two compact sentences with the scope front-loaded and the endpoint/price parenthetical parked at the end where it does not obstruct scanning. Nothing is wasted, though the listing of risk dimensions could be trimmed to a shorter phrase without losing clarity.

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?

This is a single-purpose analysis tool with no output schema, so the description must carry most of the burden of describing what comes back. It names the subject areas covered but not the shape, granularity, or confidence of the resulting summary, leaving a meaningful gap for a caller deciding how to consume the output.

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 documents all four parameters including the optional vendorName. The description adds no input-side meaning beyond the schema — the enumerated risk dimensions describe the output, not the parameters — so baseline 3 applies.

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 a specific verb+resource ('Summarize vendor email risk') and enumerates the exact risk dimensions examined: compliance claims, subprocessors, retention, DPA language, and breach notifications. No sibling tool in the catalog overlaps with vendor-email risk analysis, so the domain itself sharply distinguishes it from tools like gdpr-privacy-scan or sanctions-screen.

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?

The scope and risk dimensions imply the use case (analyzing an inbound vendor email for compliance-relevant terms), but there is no explicit when-to-use statement, no prerequisites, and no routing to an alternative tool or workflow step. A caller must infer that this is fed a vendor's email rather than, say, a vendor name alone.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources