Skip to main content
Glama
ai-ready-warehouse

ai-ready-warehouse

by KNMDeep

query

Run a single read-only SELECT or WITH statement on ai_ready-prefixed tables, capped at 5,000 rows; aggregate or add LIMIT for large tables.

Instructions

Run one read-only SELECT or WITH query. Prefix every table with ai_ready. (for example ai_ready.customers). Results are capped at 5000 rows, so aggregate or add LIMIT on large tables.

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": {
      "sql": "<sql>"
    },
    "name": "query"
  }
}

Input Schema

NameRequiredDescriptionDefault
sqlYesA single SELECT or WITH statement

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does disclose key behavior: read-only enforcement, a hard 5000-row result cap, and the mandatory ai_ready table prefix. It omits error behavior (what happens if a write statement or unprefixed table is submitted) and result format, which keeps it from a 5.

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?

Three short sentences with the core constraint first, the naming rule second, and the size caveat last. Every sentence adds a distinct, actionable fact and there is no filler.

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 tool with no output schema, the description covers the constraints an agent needs: read-only, one statement, prefix convention, and row cap. It could say more about the shape of the result set or failure modes, but nothing essential to a correct call is missing.

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?

Schema coverage is 100% and there is only one parameter, so the baseline is 3. The description adds real meaning beyond the schema: the sql value must be a single statement, and every referenced table must carry the ai_ready prefix with a concrete example.

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 gives a specific verb and resource ('Run one read-only SELECT or WITH query') and constrains scope to reads, which distinguishes it from the metadata siblings list_tables and describe_table. It stops short of naming those siblings explicitly, so an agent must infer the split.

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?

'One read-only SELECT or WITH query' establishes clear when-not conditions: no DML/DDL and no multi-statement batches. It also advises aggregating or adding LIMIT on large tables. It never names an alternative tool or says when to prefer describe_table/list_tables for exploration.

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

Deploy Server

Other Tools