Skip to main content
Glama
CelpAI

celp-mcp

Official
by CelpAI

query-database-turbo

Answer simple factual database questions using a single SQL query. Returns raw numbers or rows quickly without multi-step analysis.

Instructions

When to Use (Natural-Language Heuristics)

Because the model sees only the user's question and minimal schema hints, Turbo Mode should activate automatically whenever the request exhibits every one of these surface-level cues. Each cue corresponds to a first-principles driver of SQL complexity that the model can infer without deep schema knowledge:

Signal in the User's Question

Why It Indicates Turbo Is Safe

Single Factual Verb — verbs like "count," "list," "show," "sum," "average," or "max/min," used once.

One aggregate or projection keeps the SQL to a single SELECT.

At Most One Qualifier Clause — a lone filter such as a date range, status, or simple equality ("where status = 'active'").

Few filters avoid nested logic or subqueries.

No Comparative Language — absent words like "versus," "compare," "trend," "change over time," "prior year," "by each," etc.

Comparisons imply multiple groupings, time windows, or self-joins.

No Multi-Dimensional Grouping Phrases — avoids "by region and product," "per user per month," "split across categories."

Multiple dimensions require complex GROUP BY and often joins.

Mentions One Table-Like Concept — either explicitly ("in orders") or implicitly ("orders today," "users last week").

Referencing several entities hints at join logic the model can't verify quickly.

Requests Raw IDs or a Small Top-N List — e.g., "give me the top 5 order IDs."

The result set will be tiny, so execution latency is dominated by query planning—not data transfer.

No Need for Explanation or Visualization — the user asks only for the numbers or rows, not "explain why" or "graph this."

Generating narrative or charts costs tokens and time; Turbo avoids it.

Quick mental check: Could you answer this with a single short sentence and a single-line SQL query template? If yes, Turbo Mode is appropriate.


Limitations

  • Unsuitable for multi-step or exploratory workflows

  • May miss domain nuances captured in the standard reasoning path

  • Provides limited explanation and simplistic visuals


Effective Prompts

  • "How many active users signed up last week?"

  • "List the five most expensive orders."

  • "Show the total revenue for March 2025."

  • "What is the average session length today?"

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
promptYes
celpApiKeyNo
databaseConfigNo
databaseConnectionIdNo
Behavior3/5

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

The description discloses limitations such as unsuitability for multi-step workflows, limited explanation, and simplistic visuals. However, it lacks information about security (e.g., SQL injection risks), authentication requirements, and whether the tool is read-only. Since no annotations are provided, these gaps are significant.

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

Conciseness2/5

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

The description is excessively long, dominated by a table and detailed heuristics. It is not front-loaded with essential information; the actual purpose and parameters are missing. Every sentence does not earn its place, as many are redundant or tangential to defining the tool.

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?

Given the tool's complexity (nested objects, many parameters, no output schema), the description should explain the tool's function, input parameters, and return values. It only covers usage heuristics, leaving the agent without crucial context for invocation. The description is far from complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has 4 parameters, with 0% schema description coverage. The description does not mention any parameter, leaving the agent without guidance on what 'prompt', 'celpApiKey', 'databaseConfig', or 'databaseConnectionId' mean or how to use them. This is a critical failure for parameter semantics.

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

Purpose2/5

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

The description focuses on when to use 'Turbo Mode' rather than clearly stating what the tool does. It implies it executes database queries with optimizations, but the primary function is not explicitly defined. The verb 'query' is only in the name, not in the description.

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?

The description provides a detailed table of heuristics for when to use Turbo Mode, along with a quick mental check and example prompts. It also lists limitations. However, it does not directly compare this tool to its sibling 'query-database' or specify when not to use it in favor of alternatives.

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/CelpAI/celp-mcp'

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