Skip to main content
Glama
Risk Rule Mining MCP

Risk Rule Mining MCP

by mrezamoosavi

get_metadata

Retrieve table descriptions, grain, size, keys, and relationship coverage to understand relational financial data structure before searching or scoring rules.

Instructions

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

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.8/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden and mostly does not. It never states that the operation is read-only, what the output shape is, whether results cover all tables or a subset, or how coarse 'grain' and 'coverage' are defined. 'How tables relate' implies a relationship graph but gives no detail on whether it is inferred from keys, declared constraints, or usage.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single compact capsule with no wasted words, which is good, but the compression hurts readability: 'grain' and 'with coverage' are unexplained jargon and the whole thing is a noun phrase rather than a sentence stating an action. It is appropriately short for a zero-parameter tool, just under-clarified.

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?

For a no-parameter, no-annotation, no-output-schema tool, the description does the minimum by listing the fields returned, which partly substitutes for a missing output schema. It still leaves scope (all tables vs. filtered) and result size/pagination unaddressed, so an agent cannot predict the response volume or boundaries.

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 no parameter semantics to explain; the baseline of 4 applies. The parenthetical does usefully define some of what the response contains, but it is output content rather than input semantics.

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

Purpose3/5

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

The description names the resource (table metadata) and enumerates returned content (description, grain, size, key, relationships, coverage), which is more specific than the bare name 'get_metadata'. However, it is phrased as a noun fragment with no verb and never states scope (whole database? selected tables?), so the agent must infer that this is a read of a metadata catalog. It also makes no attempt to distinguish itself from siblings like describe_table or profile_table, whose names suggest overlapping per-table metadata.

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 when-to-use guidance at all: nothing says whether this should be called before querying, to discover tables, or to check joinability. No alternatives are named, so an agent cannot tell whether to reach for this versus describe_table, list_tables, or profile_table. The phrase 'with coverage' is the only hint of a use case (assessing metadata completeness), and it is unexplained.

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