Табуля

connections_search_tables

Read-onlyIdempotent

Semantic search over a single connection's tables — the scalable alternative to connections_get_schemas for large databases. Returns top-K tables ranked by relevance to the query (pgvector embeddings of table metadata). Get the connection_uuid from connections_list first. Signature: connections_search_tables(connection_uuid, query, space_uuid?, top_k?=20).

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

Input Schema

Name	Required	Description
`query`	Yes	Natural-language description of what to find.
`top_k`	No	Maximum number of tables to return (default 20, max 100).
`space_uuid`	No	UUID of the Tabulya space. Optional — auto-detected when you belong to exactly one space; if you belong to several, the error lists them so you can pass one.
`connection_uuid`	Yes	Connection UUID (from connections_list).

Output Schema

Name	Required	Description	Default
`tables`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 31, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already cover safety and idempotency, and the description adds useful behavioral context: results are top-K tables ranked by relevance using pgvector embeddings of table metadata. It does not discuss error handling, rate limits, or pagination, but those are less critical here given the annotations and output schema.

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

Conciseness4/5

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

The description is front-loaded and concise, with the purpose, alternative, and prerequisite stated efficiently. The explicit signature line somewhat duplicates the input schema, slightly reducing conciseness.

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 the rich schema coverage, output schema, and annotations, the description supplies everything an agent needs: purpose, scalable alternative, ranking mechanism, prerequisite, and optional parameters. No important context is missing for correct invocation.

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%, so the schema already fully documents every parameter. The description restates the signature and top_k default but adds little semantic meaning beyond what the schema provides, which matches the baseline of 3 for high-coverage schemas.

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 states a precise verb and resource: semantic search over a single connection's tables. It also distinguishes itself from the sibling connections_get_schemas by positioning itself as the scalable alternative for large databases.

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?

It explicitly names the alternative tool (connections_get_schemas) and the condition under which to prefer this one (large databases). It also gives the prerequisite of obtaining connection_uuid from connections_list first.

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

All Табуля tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?