Skip to main content
Glama
Risk Rule Mining MCP

Risk Rule Mining MCP

by mrezamoosavi

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
RRM_DATA_DIRNoDirectory where data and the database live. Defaults to ./data.

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

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}

Tools

Functions exposed to the LLM to take actions

NameDescription
list_tablesB

List loaded tables with row and column counts.

describe_tableC

Columns, types, primary key and foreign keys of one table.

profile_tableB

Column-by-column profile: role, description, nulls, distinct values, ranges, top values.

Reads saved metadata when `rrm profile` has been run, otherwise profiles on the fly.
get_metadataC

What each table is (description, grain, size, key) and how tables relate, with coverage.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

B3/5.0

Scored across 4 tools

Disambiguation4/5

The tools target mostly distinct metadata layers: table inventory, table schema, column profiling, and semantic/table-relationship metadata. There is minor overlap between get_metadata and list_tables/describe_table around table keys and descriptions, but the boundaries are reasonably clear from the descriptions.

Naming Consistency5/5

All tool names use snake_case with a leading verb and noun object: list_tables, describe_table, profile_table, get_metadata. The pattern is predictable and consistent throughout.

Tool Count4/5

Four tools is a compact, focused set for metadata discovery, and each tool covers a different exploration step. However, relative to a server named Risk Rule Mining, the set is somewhat thin because it only addresses metadata preparation.

Completeness2/5

The surface only supports table discovery, schema inspection, profiling, and metadata lookup. For a Risk Rule Mining server, there are no tools to mine, evaluate, save, or manage risk rules, leaving the core domain lifecycle unaddressed.