Skip to main content
Glama
semlayer MCP server

semlayer MCP server

table_detail

Read-onlyIdempotent

Retrieve full metadata for a specific table—columns, keys, relationships, and required filters—so AI agents can build correct queries with proper joins and filters.

Instructions

Full detail for one table: columns, keys, relationships, REQUIRED FILTERS.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "name": "<name>"
    },
    "name": "table_detail"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesThe table's `name` exactly as `get_tables`, `semantic_search` or `context_for_question` returned it. A name that is unknown, or that inference skipped, returns an explanation and not an error.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.1.1
    • addedInput schema / properties / name / description
      Added value: +"The table's `name` exactly as `get_tables`, `semantic_search` or `context_for_question` returned it. A name that is unknown, or that inference skipped, returns an explanation and not an error."
  2. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and a closed world, so the safety profile is covered. The description contributes one piece of extra behavior, signalling that returned tables carry mandatory filter constraints, but it never explains what those filters are or how they must be applied.

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?

One front-loaded line with no filler, and the highest-value item (required filters) is emphasized. The all-caps fragment is slightly telegraphic rather than fully structured, but nothing is wasted.

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 single-parameter, non-destructive read with a fully documented schema and an output schema that covers return values, the description supplies enough to call it correctly. The only real shortfall is the unelaborated 'REQUIRED FILTERS' phrase and the absence of routing guidance to sibling tools.

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?

There is a single parameter and schema coverage is 100%; the schema itself explains that the name must match what get_tables, semantic_search or context_for_question returned, and even covers the unknown-name case. The description adds nothing beyond that, 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?

The description names a specific resource ('one table') and enumerates the payload it returns: columns, keys, relationships, and required filters. That clearly distinguishes it from a listing sibling like get_tables, though it never names an alternative outright.

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?

'Full detail for one table' implies a drill-down step after a listing or search call, and 'REQUIRED FILTERS' hints the output feeds query construction, but no when-to-use or when-not-to-use condition and no named alternative are given.

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