Skip to main content
Glama
semlayer MCP server

semlayer MCP server

get_domains

Read-onlyIdempotent

Lists warehouse domains as table groupings to help you navigate available tables and select the right data for queries.

Instructions

List warehouse domains (table groupings) for navigation.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive, and closed-world, so the safety profile is fully covered by structured data. The description adds only that results serve navigation, without saying whether the list is complete, static, or scoped to a warehouse/connection. Slight added value over annotations, but not rich.

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 short sentence with the resource stated first and the clarifying parenthetical immediately after. No filler or redundant restatement of the tool name.

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 zero-argument read-only list tool with an output schema and full annotations, the description covers what is needed to invoke it correctly. The only gap is that it does not explain how domains relate to tables or whether results depend on an active connection, which matters given siblings like discover_connections.

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?

The tool takes zero parameters, so the description has nothing to disambiguate and baseline 4 applies. It correctly signals there is no filtering argument to supply.

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 warehouse domains" states a specific verb plus resource, and the parenthetical "(table groupings)" defines what a domain actually is, which the name alone would not. It does not explicitly differentiate itself from siblings like get_tables or get_metrics, so an agent must infer that domains are a coarser navigation layer.

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?

"For navigation" implies the intended role: browse structure before drilling into tables. There is no explicit when-to-use versus get_tables or table_detail, and no statement of what the agent should do next with the results.

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