Skip to main content
Glama
vic3custodio

Trade Surveillance Support MCP Server

by vic3custodio
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Server capabilities have not been inspected yet.

Tools

Functions exposed to the LLM to take actions

NameDescription
parse_email_inquiryA
Parse a user inquiry email to extract key information for investigation.

This tool analyzes email content and extracts:
- Inquiry type (trade issue, report request, data verification, etc.)
- Related trade IDs or account numbers
- Time period of interest
- Priority level
- Required actions

Args:
    email_content: The full text content of the user's inquiry email
    
Returns:
    A dictionary containing parsed information including inquiry_type,
    trade_ids, time_period, priority, and suggested_actions
search_sql_configsA
Search for SQL configuration files using metadata keywords instead of file paths.

This tool searches through indexed SQL config files by their metadata annotations.
Files should include metadata comments like:

-- @keywords: trade, transaction, daily_report
-- @type: compliance_check
-- @description: Daily trade reconciliation report

Args:
    search_keywords: Keywords to search for (e.g., "trade settlement", "compliance", "daily report")
    config_directory: Path to the directory containing SQL config files (used for initial scan)
    
Returns:
    A dictionary containing matching config files with their metadata
search_java_codeA
Search for Java classes using metadata keywords instead of file paths.

This tool searches through indexed Java files by their javadoc metadata annotations.
Java classes should include metadata in javadoc comments like:

/**
 * @keywords trade, settlement, report_generator
 * @type report_engine
 * @description Generates daily settlement reports
 */

Args:
    search_keywords: Keywords to search for (e.g., "report generator", "trade processor")
    code_directory: Path to the directory containing Java source files (used for initial scan)
    
Returns:
    A dictionary containing matching Java files with their metadata and methods
execute_java_reportA
Execute a Java unit test to generate a trade surveillance report.

This tool runs the unit test for the specified Java class with the given 
config file to generate the required report or data extract. Running tests
ensures the report generation is validated during execution.

Args:
    java_class: The fully qualified Java class name (e.g., "com.trade.SettlementReportGenerator")
    config_file: Path to the SQL config file to use
    output_directory: Directory where the report should be saved
    
Returns:
    A dictionary containing execution status, report path, and any errors
rebuild_metadata_indexA
Rebuild the metadata index by scanning all SQL configs and Java files.

Use this tool when you've added new files or updated metadata annotations.
The index is automatically built on first search, but you can manually rebuild
it with this tool.

Args:
    config_directory: Path to the directory containing SQL config files
    code_directory: Path to the directory containing Java source files
    
Returns:
    A summary of the indexing operation
generate_response_summaryB
Generate a summary response for the user inquiry with all relevant information.

This tool combines all the gathered information into a clear, actionable
response that can be sent back to the user.

Args:
    parsed_email: The parsed email inquiry data
    config_files: List of config files that were used
    report_path: Path to the generated report file
    
Returns:
    A formatted summary string ready to send to the user

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

A4/5.0

Scored across 6 tools

Disambiguation5/5

Each tool has a clearly distinct purpose with no overlap. The tools cover different stages of a workflow: parse_email_inquiry for input analysis, search_sql_configs/search_java_code for resource discovery, execute_java_report for execution, generate_response_summary for output formatting, and rebuild_metadata_index for maintenance. An agent can easily distinguish between them based on their specific functions.

Naming Consistency5/5

All tools follow a consistent verb_noun pattern with snake_case naming. The verbs are clear and descriptive (execute, generate, parse, rebuild, search), and the nouns precisely indicate the target resource or action. There are no deviations in naming conventions across the six tools.

Tool Count5/5

Six tools is well-scoped for a trade surveillance support server. Each tool serves a distinct purpose in the workflow, from inquiry parsing to report generation and response formatting. The count is neither too thin nor bloated, providing comprehensive coverage without redundancy.

Completeness4/5

The toolset covers the core trade surveillance workflow effectively: parsing inquiries, searching for relevant configurations and code, executing reports, and generating responses. A minor gap exists in direct data manipulation or validation tools (e.g., validate_trade_data, update_config), but agents can work around this using the existing search and execution tools. The surface supports end-to-end processing without dead ends.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources