Skip to main content
Glama
semlayer MCP server

semlayer MCP server

status

Read-onlyIdempotent

Check the loaded semantic layer, warehouse connections, and next action before querying; use it first to avoid claiming no data when a layer or connection exists.

Instructions

What this server has, what it can see, and what to do next.

    Call this first -- and always before telling a user you have no data
    about their warehouse. It answers with the loaded layer (its size, age, and
    how many claims nobody has reviewed yet), the warehouse connections
    visible from this machine, and a `next` field saying what to do --
    including when there is no layer at all, which is the state a fresh
    install is in. Read-only: it opens no warehouse connection and
    changes nothing.
    

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint/idempotentHint/destructiveHint=false and openWorldHint=false, so the safety profile is largely covered. The description still adds real context beyond them: it clarifies that no warehouse connection is opened (a meaningful distinction from connection-related siblings) and that the response includes a `next` recommendation, including the fresh-install/no-layer case.

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?

Front-loaded with the imperative "Call this first" and the most important precondition, then the return contents. The parenthetical about layer size/age/unreviewed claims is dense but earns its place; the phrase "what this server has, what it can see" is vague framing that adds little before the concrete sentences.

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 no-parameter, read-only status tool with an output schema, this covers the essential points: what to call it for, what states it handles (including empty), and what it will not do. Return-value detail can safely be left to the output schema, so the only residual gap is the absence of guidance on where `discover_connections` fits relative to this tool.

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 baseline is 4 and there is no parameter meaning the description could add or omit. Nothing in the description misrepresents the empty argument object.

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?

The opening line is slightly abstract ("what this server has, what it can see, and what to do next"), but the follow-up sentences make the resource concrete: loaded layer size/age/unreviewed-claim count, visible warehouse connections, and a `next` recommendation field. This clearly distinguishes it from data-fetching siblings like get_tables or run_sql, though the verb (report status) is implied rather than stated outright.

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?

Guidance is unusually explicit about ordering: "Call this first -- and always before telling a user you have no data about their warehouse." It also names a specific triggering state (fresh install, no layer at all). It does not address when a sibling such as discover_connections should be used instead, which is the only missing routing piece.

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