Skip to main content
Glama
Sign In

LunaTerminal

by com.lunaterminal
OverviewDiscussionsAdmin

Compliance screen

compliance_screen
Read-onlyIdempotent

Screen draft client communications (emails, letters, social posts, meeting notes) for common FINRA/SEC communication-rule problems, including guarantees, misleading projections, pressure tactics, testimonials, specific recommendations, tax claims, missing performance disclosures, and Social Security or account numbers. Returns a status (clear, review or revise), findings with suggested revisions, and disclosure language for the firm’s compliance review.

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

Input Schema

NameRequiredDescriptionDefault
textYesThe text to screen, up to 60,000 characters.
hasProfileNoTrue when the client has a documented risk profile on file; lowers the severity of specific recommendations.
clientFacingNoTrue (default) when the text goes to a client or the public; checks for a general risk disclosure.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, and the description is consistent with them. It adds useful output context — a three-level status, findings with suggested revisions, and disclosure language — which matters because no output schema exists.

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 sentences, front-loaded with the verb and scope, and every listed check earns its place by telling the agent what the tool detects. The category list is long and slightly run-on but remains scannable.

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?

For a three-parameter, read-only screening tool with no output schema, the definition covers inputs, checks performed, and the shape of the response. Only minor gaps remain, such as whether text is persisted or how findings are ordered.

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 coverage is 100%, so parameter meanings are already documented, including how hasProfile lowers recommendation severity and how clientFacing triggers the risk-disclosure check. The description adds the check categories but no per-parameter detail beyond what the schema provides, 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?

States a specific verb (screen) and resource (draft client communications) and enumerates the exact content types and rule categories checked. No sibling tool in the catalog performs compliance screening, so it is distinguishable without opening the schema.

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 word 'draft' and the content list (emails, letters, social posts, meeting notes) make it clear this runs before material goes to clients or the public. It does not name an alternative tool or state exclusions, but no plausible alternative exists in the sibling set.

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