Skip to main content
Glama
semlayer MCP server

semlayer MCP server

get_tables

Read-onlyIdempotent

Lists table summaries from a semantic layer, optionally filtered by domain, to help agents identify available tables for querying with business context.

Instructions

List table summaries, optionally within a domain.

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

Input Schema

NameRequiredDescriptionDefault
domainNoA domain `name` exactly as `get_domains` returned it, to list only its tables. Omit to list every table in the layer.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.1.1
    • addedInput schema / properties / domain / description
      Added value: +"A domain `name` exactly as `get_domains` returned it, to list only its tables. Omit to list every table in the layer."
  2. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

The annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety and repeatability profile is covered by structured data. The description adds only that results are summaries, not full detail; it says nothing about pagination, ordering, or result size, and an output schema exists to cover return shape.

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?

A single front-loaded sentence with the core action first and the optional modifier second; there is no redundant or filler wording.

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?

For a one-optional-parameter read tool with full annotations and an output schema, the description covers what the agent needs to invoke it correctly. The only shortfall is the missing explicit routing to table_detail for per-table detail and to get_domains for domain discovery.

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?

With 100% schema description coverage, the schema already explains that domain takes a name exactly as get_domains returned it and that omitting it lists every table. The description's 'optionally within a domain' restates that rather than adding syntax, casing, or fallback behavior, so the baseline of 3 applies.

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?

States a specific verb and resource ('List table summaries') plus an optional scope ('within a domain'), so the agent knows exactly what is returned. It does not name a sibling such as table_detail or get_domains to draw the boundary explicitly, so differentiation is left partly to the names themselves.

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

Usage Guidelines3/5

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

'optionally within a domain' implies the two usage modes (all tables vs one domain's tables), which is a reasonable contextual hint. However, it gives no explicit when-to-use-this-instead-of guidance, e.g. versus table_detail for full metadata or get_domains for discovering domains first.

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