Skip to main content
Glama
Sign In
DBHub

DBHub

by bytebase
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

search_objects

Read-onlyIdempotent

Search and list SQLite database objects—schemas, tables, views, columns, indexes, procedures, and functions—using pattern, schema, and table filters with selectable detail levels.

Instructions

Search and list database objects on the sqlite database

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": {
      "object_type": "<object_type>"
    },
    "name": "search_objects"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax results
tableNoFilter to table (requires schema; column/index only)
schemaNoFilter to schema
patternNoLIKE pattern (% = any chars, _ = one char)%
object_typeYesObject type to search
detail_levelNoDetail: names (minimal), summary (metadata), full (all)names

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.5.1

TDQS

B3.1/5.0
Behavior2/5

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

The annotations already declare readOnlyHint, idempotentHint, non-destructive, and closed-world behavior, so the safety profile is fully covered. The description adds no behavioral context beyond what the annotations and schema already provide, such as how results are ordered or whether pagination is supported.

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?

The description is a single, front-loaded sentence with no redundant or filler wording. It is efficiently sized and immediately communicates the core operation.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a six-parameter metadata-search tool with filters, enums, and detail levels, the description says nothing about how those options affect results or what the returned object list looks like. The schema fully documents the parameters and the annotations cover safety, so the definition is minimally adequate, but it misses the opportunity to explain result scope and detail-level behavior.

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 every parameter, enum, and constraint is documented in the input schema. The description adds no parameter-level meaning beyond the schema, which is the expected baseline when schema coverage is complete.

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 provides a specific verb phrase, 'Search and list database objects', and identifies the target as the sqlite database, so the purpose is clear. However, it does not explicitly distinguish this metadata-discovery operation from the sibling execute_sql, leaving the agent to infer the difference from the name.

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

Usage Guidelines2/5

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

There is no explicit guidance on when to use this tool versus execute_sql, nor any stated exclusions or prerequisites. The phrase 'Search and list' implies an introspection use case, but the agent must infer all routing decisions.

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