Skip to main content
Glama
semlayer MCP server

semlayer MCP server

route_intent

Read-onlyIdempotent

Maps an analytical intent to recommended warehouse tables to use and avoid, helping AI agents select correct tables for business queries.

Instructions

Which tables to use (and avoid) for an analytical intent.

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": {
      "intent": "<intent>"
    },
    "name": "route_intent"
  }
}

Input Schema

NameRequiredDescriptionDefault
intentYesWhat the user wants to measure, in a few plain words, such as 'monthly revenue by region'. Matched by word overlap against the layer's routing entries, and the five closest come back. Each names the tables to `use`; an `aggregates` list holds summary tables that are offered with a caveat and are not for automatic use.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.1.1
    • addedInput schema / properties / intent / description
      Added value: +"What the user wants to measure, in a few plain words, such as 'monthly revenue by region'. Matched by word overlap against the layer's routing entries, and the five closest come back. Each names the tables to `use`; an `aggregates` list holds summary tables that are offered with a caveat and are not for automatic use."
  2. First observedv0.1.0

TDQS

C2.5/5.0
Behavior2/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 safety is covered. Beyond that the description contributes only the parenthetical "(and avoid)", hinting that some tables may be discouraged, without saying how matches are ranked, how many are returned, or what the response contains.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is certainly short with no filler, but it reads as an incomplete sentence fragment rather than a front-loaded summary. Brevity here is under-specification rather than disciplined concision.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/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 needn't be explained, and the lone parameter is fully documented. However, for a routing tool sitting among roughly twenty siblings, the definition supplies no routing guidance or behavioral context, leaving the agent without enough to decide when to invoke it.

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?

Schema description coverage is 100% and the single `intent` parameter is documented richly, including overlap matching, five-closest ranking, the `use` list, and the `aggregates` caveat. The description itself adds no parameter meaning beyond the schema, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The fragment "Which tables to use (and avoid) for an analytical intent" does identify the resource (tables) and that it is intent-driven, so it isn't pure tautology. But it is a noun phrase rather than a verb+resource statement and gives no signal distinguishing it from siblings like semantic_search, get_tables, or table_detail.

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?

There is no explicit when-to-use or when-not-to-use guidance, and no named alternative among the many sibling discovery tools. The only implicit cue is "analytical intent," which leaves the agent to guess whether to call this or a table-listing/search tool first.

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