Skip to main content
Glama

data-api-code

sql_format_and_lint

Format SQL queries with uppercase keywords & clean clause newlines, and lint for SELECT *, DELETE/UPDATE without WHERE, and SQL injection string patterns.

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

Input Schema

NameRequiredDescriptionDefault
textNo
filePathNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior3/5

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

With no annotations present, the description carries the full burden, and it does add real value by naming the three concrete lint rules checked. However, it never says whether the tool only reports findings or also rewrites/mutates the input, what happens when the SQL is invalid or unparseable, or whether output includes both formatted text and a diagnostics list. For a tool with zero annotation coverage those are meaningful omissions.

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 that names the primary action first and then the lint rules; no filler or redundancy. It is dense but readable, and every clause adds information. Slightly better scaffolding (e.g., separating format from lint behavior) would push it higher.

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?

No annotations, no output schema, and two completely undocumented parameters mean the description should explain input modes and return behavior, and it does neither. It covers the lint rule set well but leaves the agent unable to decide between text and filePath or to anticipate whether the input is modified. Incomplete for a tool of this shape.

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?

Schema description coverage is 0%, so both parameters (text and filePath) are entirely undocumented, and the description does not mention either by name. It implicitly suggests passing SQL text but says nothing about filePath, whether the two are mutually exclusive, precedence between them, or why neither is required. The description does not compensate for the schema 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?

The description uses two specific verbs (format, lint) on a named resource (SQL queries) and enumerates the exact lint checks: SELECT *, DELETE/UPDATE without WHERE, and injection string patterns. This clearly separates it from siblings like sql_ddl_to_mermaid_er or xml_format_and_to_json. It stops short of explicitly stating which sibling to use when, keeping it at 4 rather than 5.

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 statement of prerequisites, and no routing to alternatives for cases this tool does not cover. The agent must infer that providing SQL is the entry point. Nothing explains whether formatting and linting are always both performed or can be requested independently.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources