BaseQL MCP Server

searchTable

Search records by exact, case-sensitive match on string fields. Control which fields to search; returns up to 100 results.

Instructions

Search for records by exact, case-sensitive matches on string fields. This is not full-text search; it filters specific fields (use fields to control which). If you need case-insensitive or partial matching, BaseQL does not support it directly.

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": {
      "tableName": "<tableName>",
      "searchTerm": "<searchTerm>"
    },
    "name": "searchTable"
  }
}

Input Schema

Name	Required	Description
`limit`	No	Maximum number of results to return (default: 10, max: 100)
`fields`	No	Specific string fields to search. If omitted, the tool uses common string fields that exist in the table.
`tableName`	Yes	The name of the table to search
`searchTerm`	Yes	Case-sensitive search term to match exactly

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.0.0Aug 13, 2026

TDQS

A4.2/5.0

Behavior3/5

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

With no annotations, the description carries the full burden. It discloses that matching is exact, case-sensitive, and limited to string fields, which is key behavioral info. However, it omits return format, pagination behavior, or error handling, leaving some transparency gaps.

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?

Two sentences total; the first states the core function, the second clarifies limitations and unsupported cases. No redundancy, perfectly front-loaded.

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?

Given no output schema and no annotations, the description covers purpose, limitations, and parameter usage adequately. It doesn't need to explain return values since there's no output schema, but it could mention behavior for missing results or defaults.

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 covers all 4 params with descriptions, so baseline is 3. Description adds meaning by instructing 'use fields to control which' and restricting to string fields, providing extra semantics beyond the schema.

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?

Description uses 'Search' with specific verb+resource: 'Search for records by exact, case-sensitive matches on string fields.' It clearly distinguishes from full-text search by explicitly stating 'This is not full-text search.' This sets it apart from sibling tools like query or queryTable.

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?

Provides clear context: use for exact, case-sensitive matches, and explicitly excludes unsupported case-insensitive or partial matching. It doesn't name alternative tools but clarifies the boundary with 'BaseQL does not support it directly,' giving enough guidance for an agent.

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

Deploy Server