Skip to main content
Glama
Risk Rule Mining MCP

Risk Rule Mining MCP

by mrezamoosavi

profile_table

Profiles each table column for roles, nulls, distinct values, ranges, and top values, using saved metadata when available and profiling on demand otherwise.

Instructions

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.

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": {
      "table": "<table>"
    },
    "name": "profile_table"
  }
}

Input Schema

NameRequiredDescriptionDefault
tableYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose one important behavior: it reads precomputed metadata when `rrm profile` was run, otherwise it profiles live. That hints at a potentially expensive full-data scan, but cost, latency, permissions, and failure modes are never stated.

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 short lines, output contents front-loaded, no filler. The second sentence is slightly cryptic in referencing `rrm profile` without explaining what that command is, but nothing is wasted.

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?

An output schema exists, so return-value explanation isn't required, and the enumeration of profile fields is a bonus. However, for a profiling tool that may scan data, the description omits the table identifier format and any indication of cost or runtime, leaving real gaps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

There is a single required parameter `table` with 0% schema description coverage, and the description says nothing about its expected format (bare name vs. fully-qualified dataset.table) or case sensitivity. The only parameter is effectively undocumented in both schema and prose.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific operation (column-by-column profile) and enumerates the concrete outputs: role, description, nulls, distinct values, ranges, top values. That implicitly separates it from siblings like describe_table or get_metadata by signaling statistical profiling rather than plain schema description, though no sibling is named explicitly.

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?

Usage is only implied — an agent can infer this is the tool for column statistics, but there is no explicit 'use this when X, use describe_table when Y' guidance and no stated prerequisites. The note about saved metadata is behavioral rather than a when-to-use rule.

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

Deploy Server

Other Tools