Elekto MCP for SQL Server

Official

Overview Schema Source Related Servers Discussions Admin

Find columns by name

find_columns

Read-onlyIdempotent

Locate all tables and views containing a matching column, with type and nullability, to assess rename or widening impact.

Instructions

Finds every table and, by default, every view holding a column whose name matches a pattern, with each column's type_declaration and nullability. Use it to answer 'which objects have this column?' before a rename, a widening or an impact review; to find objects by their own name use list_tables or list_views.

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": {
      "database": "<database>",
      "column_pattern": "<column_pattern>"
    },
    "name": "find_columns"
  }
}

Input Schema

Name	Required	Description
`schema`	No	Restrict to one schema. Empty means every schema. Example: 'Feeder'
`database`	Yes	Name of the database as registered in the configuration.
`include_views`	No	Include views as well as tables. True by default.
`column_pattern`	Yes	Part of a column name. A pattern without % matches anywhere in the name, so 'Date' finds ReferenceDate and AuxDate; add % yourself for a prefix or suffix match, as in 'Aux%'. Example: 'ReferenceDate'

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 4, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and a closed-world scope, so safety is covered. The description still adds behavioral value by disclosing the default inclusion of views and the content of each result (type_declaration and nullability).

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 tight clauses: the capability first, then the routing guidance. No filler, and the scope constraint (tables plus default views) is front-loaded.

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 no output schema present, the description compensates by naming the returned fields (type_declaration, nullability) and the default view behavior. Combined with the fully documented input schema and safety annotations, an agent has everything needed to call it correctly.

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 description coverage is 100%, so the schema already documents all four parameters in detail, including the unanchored pattern semantics and the schema default. The description only echoes the view default and adds no parameter detail beyond the schema — the expected baseline of 3.

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?

States a specific verb and resource: finds every table and (by default) every view holding a column matching a name pattern. It also names the sibling tools (list_tables, list_views) that find objects by their own name, so an agent can discriminate without opening a schema.

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?

Gives explicit scenarios — before a rename, a widening, or an impact review — and explicitly routes the alternative case ('to find objects by their own name') to list_tables or list_views. When and when-not are both covered.

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