Skip to main content
Glama
Sign In

SQL Server MCP by InsightfulPipe

by com.insightfulpipe
OverviewDiscussionsAdmin

mssql Prompts

prompts_menu
Read-only

Access mssql prompt catalog with 4 operations:

  1. List Public Prompts: • request='menu' - No additional params needed • Returns: All public/system prompts available for mssql

  2. List Custom Prompts: • request='menu', prompt_type='custom', workspace_id= • Returns: All custom prompts for the specified workspace

  3. Get Public Prompt Details: • request='prompt_details', prompt_id= • Returns: Full text/details of a public prompt

  4. Get Custom Prompt Details: • request='prompt_details', prompt_id=, is_custom=True, workspace_id= • Returns: Full text/details of a custom prompt

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": {
      "request": "<request>"
    },
    "name": "prompts_menu"
  }
}

Input Schema

NameRequiredDescriptionDefault
requestYes
is_customNo
prompt_idNo
prompt_typeNo
workspace_idNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

readOnlyHint=true already declares the safety profile, so the description adds little on that axis. The per-operation 'Returns:' lines hint at output shape, but an output schema exists and no auth, rate-limit, or pagination behavior is described.

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

Conciseness4/5

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

Front-loaded with the operation count, then numbered entries with params and returns; each line earns its place. Slightly repetitive with the 'Returns:' sub-bullets, but the scanning structure is a net positive.

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?

With an output schema covering returns and annotations covering read-only safety, the main remaining gap was parameter dispatch, which the description handles completely. Nothing critical is missing for a correct call.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description carries the full burden, and it does well: all five parameters appear in context, with is_custom and workspace_id correctly tied to the custom-prompt branches. Only prompt_type's full value domain (beyond 'custom') is left implicit.

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 names a specific resource (mssql prompt catalog) and enumerates four concrete operations with the exact request values that select them. It is clearly distinguishable from siblings like execute_action and query_data, though it never explicitly contrasts itself with them.

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?

Each mode is paired with the precise parameter combination that triggers it (e.g., request='menu' + prompt_type='custom' + workspace_id for custom lists), which is strong selection guidance. It stops short of saying when *not* to use this tool or how it differs from the other prompt/context tools.

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

All SQL Server MCP by InsightfulPipe toolsInspect
Try in Browser
Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources