Skip to main content
Glama
Risk Rule Mining MCP

Risk Rule Mining MCP

by mrezamoosavi

describe_table

Retrieves a table’s column names, data types, primary key, and foreign keys so you can inspect its relational structure before building or querying risk rules.

Instructions

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

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

Input Schema

NameRequiredDescriptionDefault
tableYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.4/5.0
Behavior2/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, and it discloses almost nothing: read-only nature is only implied, and there is no mention of behavior for nonexistent tables, schema qualification, permission requirements, or what the response looks like. For a metadata inspection tool this is a notable gap.

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?

It is short and front-loaded, but it is a noun-phrase fragment rather than a statement of action, and its brevity comes at the cost of substantive information rather than from efficient editing.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a one-parameter tool the description is thin: it omits how the table argument should be formed, error behavior, and how the tool relates to three sibling metadata tools. An output schema is absent, yet the description only partially enumerates return fields.

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?

The single parameter has 0% schema description coverage, leaving the description to explain it, yet the description only implies that 'table' identifies the table. It does not say whether a schema-qualified or fully-qualified name is accepted, or how ambiguous names are resolved.

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 fragment names a specific resource and enumerates the returned metadata (columns, types, primary key, foreign keys), so the agent can infer intent. But it lacks a verb and does not distinguish itself from siblings like profile_table or get_metadata, which plausibly overlap.

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, no prerequisites, and no mention of when to prefer profile_table or get_metadata instead. The agent must guess the boundary between these tools from their names alone.

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