Skip to main content
Glama
SynapCores MCP Server

SynapCores MCP Server

Official

List tables

list_tables
Read-onlyIdempotent

Lists tables in a SynapCores database, with optional LIKE pattern filtering, so you can discover available data before writing SQL queries.

Instructions

List the tables in a SynapCores database, optionally filtered by a LIKE-style name pattern, and return {database, tables: [{name}], count}. Use it to discover what exists before writing SQL; use describe_table for a table's columns and types. Internal tables (names starting with "_") are hidden unless include_system=true. Read-only.

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_tables"
  }
}

Input Schema

NameRequiredDescriptionDefault
patternNoName filter with LIKE wildcards: % matches any run of characters, _ matches one character (for example 'order%').
databaseNoDatabase name; omit to use the default database.
include_systemNotrue = also list internal tables whose names start with '_' (default false).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.0.1
    • changedInput schema / properties / database / description
      Previous value: -"Database name (optional, uses default)"New value: +"Database name; omit to use the default database."
    • changedInput schema / properties / include_system / description
      Previous value: -"Include system tables (default: false)"New value: +"true = also list internal tables whose names start with '_' (default false)."
    • changedInput schema / properties / pattern / description
      Previous value: -"Filter pattern (SQL LIKE syntax)"New value: +"Name filter with LIKE wildcards: % matches any run of characters, _ matches one character (for example 'order%')."
  2. First observedv1.0.0

TDQS

A4.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 and destructiveHint=false, so the trailing 'Read-only' adds nothing structured data doesn't. The genuinely additive detail is the default hiding of internal '_'-prefixed tables unless include_system=true, which is real behavioral context an agent would otherwise miss, but nothing is said about result limits or ordering.

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?

Three dense sentences, each front-loading the essential information (action, then guidance, then hidden-table caveat). The closing 'Read-only' is the one sentence that doesn't earn its place because the annotations already state it.

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?

There is no output schema, and the description compensates by naming the exact returned object shape. With the sibling routing, the system-table caveat, and the default-database option all covered, nothing an agent needs to invoke this correctly is missing.

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 the LIKE wildcard semantics, the optional database, and the include_system default. The description merely restates 'optionally filtered by a LIKE-style name pattern' and the system-table rule, adding no new syntax or edge-case meaning beyond the schema baseline.

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 (list) and resource (tables in a SynapCores database), plus the optional filter and the exact return shape {database, tables, count}. It explicitly separates itself from describe_table, so an agent can choose without opening either 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 a concrete use case ('discover what exists before writing SQL') and names the alternative for a different need ('use describe_table for a table's columns and types'). The routing decision between the two sibling tools is unambiguous.

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