Skip to main content
Glama
Sign In
MSSQL MCP Reader

MSSQL MCP Reader

by ConnorBritain
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

inspect_dependencies

Identify database objects that depend on a table, view, or other object for impact analysis before schema changes.

Instructions

Shows what database objects depend on a table, view, or other object. Use for impact analysis before schema changes.

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": {
      "objectName": "<objectName>"
    },
    "name": "inspect_dependencies"
  }
}

Input Schema

NameRequiredDescriptionDefault
objectNameYesName of the object to inspect (e.g., 'dbo.Customers' or 'Customers')
includeColumnsNoInclude column-level dependency details. Default: false
environmentNoOptional environment name to target.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.2

TDQS

A3.7/5.0
Behavior2/5

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

No annotations exist, and the description only states function without disclosing behavioral traits like read-only nature, permissions needed, error handling, or side effects. The agent lacks insights beyond basic purpose.

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 sentences with no wasted words. First sentence clearly states function, second adds use case. Perfectly 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?

Description explains what and when to use, but missing details on return format, error cases, and behavior for invalid inputs. With no output schema or annotations, the description is only partially complete.

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 parameters are already well-documented. The description adds no extra meaning to parameters beyond what the schema provides, meeting the baseline for high 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?

Description clearly states the tool shows dependencies and is used for impact analysis, with a specific verb 'shows' and resource 'database objects'. It distinguishes from siblings like describe_table and inspect_relationships.

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?

Explicitly states 'Use for impact analysis before schema changes', providing clear context. While it doesn't list exclusions or alternatives, the sibling tools list implies different purposes.

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