Skip to main content
Glama
semlayer MCP server

semlayer MCP server

get_metrics

Read-onlyIdempotent

Lists defined metrics with their name, measure, aggregation, and filter so AI agents can select the right business metric for warehouse queries.

Instructions

List defined metrics (name, measure, aggregation, filter).

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/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 openWorldHint=false, so the safety profile is fully covered without prose. The description adds only the shape of each returned entry, and since an output schema exists even that is largely redundant.

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?

A single front-loaded sentence with the resource stated first and the return fields compactly bracketed; no filler or repetition. It is arguably under-specified rather than over-long, so it earns high marks here while losing ground on completeness.

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?

With no parameters, a simple read-only annotation set, and an output schema that documents the return shape, there is little an agent still needs. The one real gap is relational: nothing connects this listing tool to compile_metric or explains the workflow it belongs to.

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, which is the baseline-4 case: the empty input schema is fully described at 100% coverage and there is nothing for the description to clarify. The parenthetical field list refers to output, not input, so it does not add parameter meaning.

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 defined metrics" gives a specific verb plus resource, and the parenthetical enumerates the fields each entry exposes (name, measure, aggregation, filter), so the agent knows exactly what kind of object comes back. It does not name a contrasting sibling such as compile_metric, which is the main thing keeping it from a 5.

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

Usage Guidelines2/5

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

The description says what the tool returns but never states when to reach for it instead of compile_metric, semantic_search, or table_detail. An agent must infer that this is the discovery step before compiling a metric; no exclusion or precondition is offered.

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