Skip to main content
Glama
Secure MySQL MCP Server

Secure MySQL MCP Server

by Kavi-200312

get_table_relationships

Inspect foreign key relationships and table constraints, optionally filtered by database or table, to understand schema dependencies.

Instructions

Inspect foreign key relationships and table constraints.

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_table_relationships"
  }
}

Input Schema

NameRequiredDescriptionDefault
tableNoOptional specific table to filter relationships.
databaseNoOptional database name.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations provided, the description carries the full burden, and it discloses almost nothing: 'Inspect' implies a read, but there is no statement about permissions, whether omitting both filters returns everything or errors, or what the result looks like. For a metadata tool this is thin but not misleading.

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 or redundancy. It is efficient, though its brevity is also the source of the missing behavioral detail.

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?

A simple read tool with two optional, fully documented params and no output schema or annotations needs less prose, so this is close to adequate. The unfilled gap is default scope (all databases vs. current one) and any failure mode for an unknown table name.

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

Parameters3/5

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

Schema coverage is 100% and both parameters are documented as optional filters, so the schema does the work. The description adds no meaning beyond it — notably it never explains the scope when 'database' and 'table' are both omitted, which is the one semantic gap.

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?

Specific verb ('Inspect') plus concrete resources ('foreign key relationships and table constraints'), which goes beyond the tool name and tells the agent exactly what data it yields. It does not, however, distinguish itself from describe_table or get_database_overview, which likely touch overlapping 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?

No when-to-use guidance, no exclusions, and no named alternative (e.g. 'use describe_table for column types'). The agent must infer that this is the metadata tool to reach for when FK/constraint information is needed.

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