Skip to main content
Glama
semlayer MCP server

semlayer MCP server

discover_connections

Read-onlyIdempotent

Lists warehouses reachable from this machine by name without reading credentials or opening connections, and checks whether a named warehouse is supported or what route it needs.

Instructions

Which warehouses are reachable from this machine, by name.

    Reads DuckDB files in the working directory, warehouse environment
    variables, `$SEMLAYER_HOME/.env`, dbt's profiles.yml and Snowflake's
    connections.toml. Names only: no credential is read, no value that
    could be one is reported, and no connection is opened. Each entry says
    whether semlayer can open it (`supported`) and what it would need if
    not (`note`).

    requested: the warehouse the user NAMED, in their words, when it is
    not in the list -- "databricks", "our iceberg tables in s3", "redshift".
    The answer says whether semlayer opens it after all (Redshift is the
    postgres connection), and if not, the nearest route and what to tell
    them. Pass it rather than guessing: a wrong guess here is either a
    promise we cannot keep or a user sent away who did not need to be.
    

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

Input Schema

NameRequiredDescriptionDefault
requestedNoThe warehouse the user named, in their own words, when it is not in the list: 'databricks', 'redshift', 'our iceberg tables in s3'. Omit it to list what is reachable.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.1.1
    • addedInput schema / properties / requested / description
      Added value: +"The warehouse the user named, in their own words, when it is not in the list: 'databricks', 'redshift', 'our iceberg tables in s3'. Omit it to list what is reachable."
  2. First observedv0.1.0

TDQS

A4.6/5.0
Behavior5/5

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

Goes well beyond the readOnly/idempotent/non-destructive annotations by disclosing exactly which files and environment sources are read, that no credentials are read or reported, and that no connection is opened. It also explains the shape of each entry (`supported`, `note`) and what happens for a named-but-unsupported warehouse (Redshift resolving to the postgres connection).

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?

Purpose and safety guarantees are front-loaded, and the paragraph on `requested` is clearly scoped. Some phrasing is rhetorical rather than informational ('a promise we cannot keep or a user sent away'), and the parameter discussion overlaps the schema text, costing a little economy.

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?

An output schema exists, so return values need not be detailed, yet the description still sketches entry fields. For a single-optional-parameter read-only discovery tool, an agent has everything needed to decide to call it and how to populate `requested`.

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?

Schema coverage is 100%, so the schema already carries the baseline; the description nonetheless adds meaning by framing `requested` as the user's own words, giving real-world phrasing examples, and explaining the downstream consequence (nearest route and what to tell the user) of supplying it.

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?

Opens with a specific verb and resource: 'Which warehouses are reachable from this machine, by name.' It then enumerates the concrete sources it inspects (DuckDB files, env vars, `.env`, profiles.yml, connections.toml), which distinguishes it cleanly from data-oriented siblings like get_tables or status.

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?

It states when to use the optional argument ('the warehouse the user NAMED ... when it is not in the list') and warns explicitly against guessing, with the failure modes spelled out. It does not name sibling tools or state when another tool is the better choice, so it stops short of a 5.

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