mssql-dba-mcp

Get Collation Mismatches

mssql_db_collation_mismatches

Read-onlyIdempotent

Find dbo schema columns with collations differing from the database default, which cause collation conflict errors when joining with temp tables.

Instructions

Collation mismatches: columns (dbo schema) whose collation differs from the database default. A common cause of collation conflict errors in joins with temp tables.

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

Input Schema

Name	Required	Description	Default
`databaseName`	No	Target database. Defaults to connected database.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 20, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already declare this as a safe, read-only, idempotent operation, so the description's added value is in disclosing the scan scope (dbo schema columns only) and the comparison basis (database default collation). It stops short of describing return shape or any rate limits, but adds meaningful behavioral context beyond the annotations.

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?

Two short sentences, front-loaded with the core definition and followed by a brief diagnostic rationale. No filler or redundancy.

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

Completeness4/5

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

For a simple read-only listing tool with full schema coverage and rich annotations, the description explains what is returned and why it matters. It does not enumerate result columns, but an output schema is absent and the description is still sufficient for correct invocation.

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 the single databaseName parameter is fully documented by the schema itself. The description adds no additional syntax, format, or default behavior beyond what the schema already provides.

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 clearly identifies the resource (collation mismatches among columns) and narrows scope to the dbo schema and database default. It effectively distinguishes itself from the sibling mssql_db_collation, but lacks an explicit verb and does not name alternatives.

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?

The diagnostic note 'A common cause of collation conflict errors in joins with temp tables' implies when the tool is useful, but there is no explicit when-to-use instruction, prerequisite, or comparison to sibling tools.

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

Deploy Server