Skip to main content
Glama
Risk Rule Mining MCP

Risk Rule Mining MCP

by mrezamoosavi

list_tables

Inspect loaded financial tables with row and column counts to confirm available data before searching for explainable risk rules.

Instructions

List loaded tables with row and column counts.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_tables"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full behavioral burden. Hinting that it lists 'loaded' tables implies a read operation within an active context, but it never states that the operation is read-only, what 'loaded' means (session, connection, catalog), or what happens when nothing is loaded.

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?

A single front-loaded sentence with no filler, and the payload (row and column counts) comes after the action. It is efficient but arguably too sparse for its role as an entry point into the table-navigation siblings.

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 the description need not explain return values, and with no parameters the schema burden is minimal. However, for a discovery tool sitting alongside describe_table and get_metadata, it omits the one thing an agent needs: the scope of 'loaded' and how it fits the exploration workflow.

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

Parameters4/5

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

The tool takes zero parameters, so there is nothing for the description to disambiguate; the baseline of 4 applies. The schema coverage is 100% and the input schema is an empty object, so no gap needs filling.

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 states a specific verb and resource ('List loaded tables') and adds what is returned ('row and column counts'). It does not explicitly contrast with siblings such as describe_table or get_metadata, so sibling differentiation is left to inference.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no guidance on when to use this tool versus describe_table, get_metadata, or profile_table, and no stated prerequisites or exclusions. The only implied signal is the word 'loaded', which suggests a scoping condition but is never explained.

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