Skip to main content
Glama
Jambozx

OnlineCyberTools MCP (280+ filterable tools)

webdev_sql_formatter

Read-onlyIdempotent

Reformat SQL statements with consistent indentation and keyword casing, and retrieve query statistics without connecting to a database.

Instructions

SQL Formatter and Beautifier. Reformat a SQL statement or script with consistent indentation and keyword casing, and report query statistics. Use webdev_graphql_formatter for GraphQL or webdev_json_formatter for JSON. This is a purely syntactic beautifier: it never connects to a database, runs a query, or validates that the SQL executes. Runs locally on the text you provide: read-only, non-destructive, contacts no external service, and is rate-limited (60 requests/minute for anonymous callers). Returns the formatted SQL plus statistics (keyword count, line count, referenced table names, and byte sizes).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sqlYesThe SQL statement or script to format. Must not be blank.
formatNoWhen true, reindent via the sql-formatter engine; when false, only apply keyword casing.
uppercaseNoUpper-case SQL keywords (SELECT, FROM, WHERE); when false, preserve original casing.
indentSizeNoNumber of spaces per indent level (used only when indentType is spaces).
indentTypeNoIndent with spaces (honouring indentSize) or with a single tab per level.spaces
addSemicolonNoAppend a trailing semicolon when the statement does not already end with one.
removeCommentsNoStrip block (slash-star) and line (double-dash) comments before formatting.
compactModeNoCollapse the SELECT field list onto a single line instead of one column per line.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
originalNoThe submitted SQL, echoed back.
formattedNoThe reindented or recased SQL output.
statsNoSize and content metrics for the statement.
Behavior5/5

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

Annotations already declare read-only, non-destructive, and idempotent. Description adds rate-limiting (60 req/min), local execution, and that it returns formatted SQL plus statistics. No contradictions.

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

Conciseness5/5

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

Three sentences, front-loaded with purpose, no unnecessary words or repetition.

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

Completeness5/5

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

With rich schema, annotations, and output schema, the description covers the tool's scope, limitations, and behavior completely. It differentiates from siblings and explains what it does and does not do.

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%, so baseline is 3. Description does not add new parameter info beyond what schema provides; statistics mention is about output, not parameters.

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

Purpose5/5

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

Description clearly states it's a SQL formatter/beautifier that reformats SQL with consistent indentation and keyword casing, and reports statistics. It explicitly distinguishes itself from sibling tools webdev_graphql_formatter and webdev_json_formatter.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly says to use for SQL formatting, and to use webdev_graphql_formatter for GraphQL and webdev_json_formatter for JSON. Also clarifies it never connects to a database, so it's safe for any SQL text.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Jambozx/onlinecybertools-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server