Skip to main content
Glama
Sign In
tibero-mcp

tibero-mcp

by jdk1021
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

list_tables

Read-only

Lists tables and views in a schema with their comments and approximate row counts, supporting search and paging to explore database structure.

Instructions

List tables (and views) in a schema with their comments and approximate row counts.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_tables"
  }
}

Input Schema

NameRequiredDescriptionDefault
offsetNoRows to skip; pass next_offset from a truncated result to page.
schemaNoSchema (owner). Defaults to the connected user.
searchNoCase-insensitive text matched against table names and comments.
include_viewsNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds useful context beyond them — that views are included and that row counts are approximate — but says nothing about result truncation or default page size, which matters for a listing tool.

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?

A single front-loaded sentence carrying scope, inclusion of views, and returned fields with zero filler. Nothing could be removed without losing information.

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 read-only listing tool with an output schema and mostly documented parameters, the definition is nearly sufficient. The one gap is that truncated results and paging behavior are only discoverable through the offset parameter's own description, not the tool description.

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 coverage is 75% and offset, schema, and search are well documented inline. The description contributes meaning only for include_views (via "and views"), signaling views are returned by default; the rest is already in the schema, so the baseline of 3 holds.

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?

"List tables (and views) in a schema" names a specific verb and resource, and adds the payload (comments, approximate row counts). It is clearly distinct from list_schemas and describe_table, though it never explicitly names a sibling to contrast with.

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 when-to-use guidance: nothing says to prefer this over search_columns for name lookups or describe_table for a single table's structure. The only implied usage comes from the word "List" and the search parameter, leaving the agent to infer routing.

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