Skip to main content
Glama
surinch-db-guard

surinch-db-guard

ddl_governance_check

Scores CREATE TABLE DDL for MySQL, PostgreSQL, or Doris across five weighted governance dimensions and returns a SHA-256 verifiable receipt, rejecting empty, invalid, or unsupported input.

Instructions

Score CREATE TABLE DDL (MySQL/PostgreSQL/Doris) across 5 weighted governance dimensions with SHA-256 verifiable receipt. Rejects empty/invalid input or unsupported dialect.

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": {
      "ddl": "<ddl>"
    },
    "name": "ddl_governance_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
ddlYesSanitized CREATE TABLE DDL text (no production credentials or row data).
dialectNomysql

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/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. It does disclose useful edge behavior (rejects empty/invalid input and unsupported dialects) and mentions a verifiable receipt, but it never enumerates the 5 governance dimensions, their weights, score ranges, determinism, or whether any state is written — the core of what this tool actually returns.

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 dense sentences with the core capability front-loaded and no filler. The only mild redundancy is re-listing the three dialects, which the enum already encodes.

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 scoring tool with no output schema and no annotations, the description should say more about the result structure. It states that 5 weighted dimensions and a receipt exist but leaves the agent unable to anticipate the response shape or interpret scores.

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 50%: the ddl parameter is documented in the schema, while dialect has only an enum and default. The description's dialect list (MySQL/PostgreSQL/Doris) reinforces the enum but adds no new constraint, and it says nothing about how dialect changes the scoring rubric.

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 opens with a specific verb and resource ('Score CREATE TABLE DDL'), scopes it to three dialects, and states the output nature (5 weighted governance dimensions plus a SHA-256 receipt). It is clearly distinguishable in substance from siblings like sql_readonly_review, though it never names or contrasts them 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 implied by the resource type: use it to score CREATE TABLE DDL. There is no explicit when-to-use/when-not guidance and no routing to the sibling tools, so an agent must infer whether to pick this over sensitive_masking_scan or sql_readonly_review.

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