Skip to main content
Glama
us-all
by us-all

search-tools

Discover dbt MCP tools by describing your task in natural language. Search across artifact, quality, and meta categories to find the tool you need.

Instructions

Discover available dbt MCP tools by natural language query across dbt / quality / meta categories.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesNatural language query. Discover available dbt MCP tools across dbt artifact / DQ result table / meta categories — call this first to find the right tool.
categoryNoRestrict search to a specific category
limitNoMax results (default 20)
Behavior4/5

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

No annotations provided, but description implies a safe, read-only search operation. Could explicitly state no side effects, but current description is adequate for a search tool.

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

Conciseness5/5

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

Single sentence with all key information: purpose, input type, and scope. No superfluous text.

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?

Given simple search tool with 3 params and no output schema, the description fully covers what the tool does and when to use it.

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?

Description adds value beyond schema, e.g., 'call this first' context for query parameter, and category enum restriction. Schema coverage is 100%, so description complements well.

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?

The description clearly states it discovers dbt MCP tools by natural language query across categories, distinguishing it from sibling tools which are specific functionalities.

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

Usage Guidelines5/5

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

Explicitly says 'call this first to find the right tool', providing clear guidance on when to use it as a discovery tool before selecting siblings.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/us-all/dbt-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server