Skip to main content
Glama
neverinfamous

MySQL MCP Server

MySQL CONCAT

mysql_concat
Read-only

Concatenate values from multiple columns into one string with a custom separator, useful for combining fields directly in a MySQL query.

Instructions

Concatenate multiple columns with an optional separator.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoAlias for table
aliasNoResult column nameconcatenated
limitNoMaximum number of rows to return
tableNoTable name (Note: Pass a table name, not a raw string)
whereNoAdditional WHERE clause for filtering
filterNoAlias for where
columnsNoColumns to concatenate (Note: Pass column names, not raw strings)
separatorNoSeparator between values
tableNameNoAlias for table
includeSourceColumnsNoInclude individual source columns in output (default: false). Set to true for full context.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
codeNoError code (e.g. VALIDATION_ERROR, QUERY_ERROR)
dataNo
errorNoError message if operation failed
detailsNoAdditional error context
metricsNoToken estimation metrics
successYesWhether the operation succeeded
categoryNoError category (validation, query, connection, internal)
suggestionNoSuggested fix for the error
recoverableNoWhether the error is recoverable
Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the description's claim of 'concatenate' aligns with read-only behavior. However, no additional behavioral traits (e.g., that it works on string columns, returns a new column) are disclosed beyond what annotations provide.

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?

The description is a single sentence that conveys the core purpose without any redundant information. It is front-loaded and efficient.

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?

With 10 parameters and an output schema present, the description lacks usage context, examples, or prerequisites. An agent may need additional guidance on how to apply parameters like 'includeSourceColumns' or 'filter'.

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% with 10 parameters described. The description highlights 'multiple columns' and 'optional separator', which map to the 'columns' and 'separator' parameters, but does not add extra meaning beyond the schema definitions. Baseline 3 is appropriate.

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?

The description clearly states the verb 'Concatenate' and the resource 'multiple columns with an optional separator'. It is specific and distinguishes itself from sibling tools like mysql_json_* that handle JSON concatenation.

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?

The description provides no guidance on when to use this tool versus alternatives, such as when to use mysql_concat vs mysql_json_merge for JSON arrays. No when/when-not or alternative recommendations are given.

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/neverinfamous/mysql-mcp'

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