Skip to main content
Glama
sql-mcp
by ohankay

list_objects

Read-onlyIdempotent

Lists SQL Server objects such as tables, views, procedures, functions, triggers, synonyms, and sequences, with optional schema, database, type, and name-pattern filters for schema discovery.

Instructions

List user objects. object_type: table|view|procedure|function|trigger|synonym|sequence (omit = all). name_like uses LIKE syntax, e.g. 'Customer%'.

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

Input Schema

NameRequiredDescriptionDefault
schemaNo
databaseNo
max_rowsNo
name_likeNo
connectionNo
object_typeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, so the safety profile is covered. The description adds genuine behavioral detail: omitting object_type returns all object kinds, and name_like follows LIKE wildcard syntax. It omits a behaviorally significant fact, however: max_rows defaults to 2000, so results may be silently capped.

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?

Two compact sentences with no filler, and the core action is front-loaded before the parameter notes. The parenthetical defaults are efficient shorthand rather than wasted words.

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?

For a six-parameter read tool with no output schema, the description covers the filtering semantics but not the return shape, whether the result list is truncated at max_rows, or how connection scoping works. Adequate to invoke, but not enough to predict what comes back.

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 0%, so the description carries the parameter burden and does cover the two least obvious ones: object_type with all seven valid values plus its omit-to-get-all default, and name_like with an example pattern. The other four parameters (schema, database, connection, max_rows) get no explanation at all despite the zero coverage, leaving the compensation incomplete.

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?

"List user objects" gives a specific verb and resource, and the object_type enumeration makes the scope concrete (tables, views, procedures, etc.). It does not distinguish itself from siblings such as describe_table or get_object_definition, so an agent must infer when metadata listing stops and definition retrieval begins.

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

Usage Guidelines2/5

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

There is no explicit when-to-use or when-not-to-use guidance and no named alternative. The filtering options imply a discovery use case, but nothing tells the agent to prefer describe_table for column-level detail or list_databases when it doesn't yet know the database.

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