Skip to main content
Glama
Sign In
sqlserver

sqlserver

by AshwathDAzur
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

execute_query

Executes SQL SELECT queries on SQL Server and returns the resulting data.

Instructions

Execute a SQL query and return results. Use for SELECT queries to retrieve data.

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": {
      "query": "<query>"
    },
    "name": "execute_query"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesThe SQL query to execute (SELECT only)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.8/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It mentions executing a query and returning results, and says 'Use for SELECT queries', which implies a read-only nature, but does not explicitly state that it cannot modify data, nor does it mention side effects, permissions, or return format specifics.

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 two short sentences with no unnecessary words. It conveys the primary purpose and usage context succinctly, earning a perfect score for conciseness.

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?

Given the tool's simplicity (one parameter, no output schema), the description is adequate: it explains the action, the return of results, and the applicable query type. It lacks a few details like explicit read-only assurance, but overall it is sufficiently complete for straightforward usage.

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?

The schema has 100% parameter description coverage with 'The SQL query to execute (SELECT only)'. The description adds no significant semantic meaning beyond what the schema already provides, though it does reinforce the SELECT-only constraint. Baseline of 3 is appropriate given full schema coverage.

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 tool executes SQL queries and returns results, specifically for SELECT queries to retrieve data. This distinctly separates it from siblings like execute_insert and execute_update, which handle mutations, and from metadata tools like list_tables.

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

Usage Guidelines4/5

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

The description provides explicit guidance to use this tool for SELECT queries, clearly indicating the appropriate use case. It does not explicitly mention alternatives or exclusions, but the intended context is strongly implied, making it effective.

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

Deploy Server

Other Tools