Skip to main content
Glama
Sign In
b1-mcp-server

b1-mcp-server

by Anand95r
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

get_schema_info

Retrieves table, column, or procedure metadata from a connected database so you can explore the schema and confirm targets before writing queries. Read-only.

Instructions

Retrieve metadata about tables, columns, or procedures in the currently connected database. Read-only. Use this to explore the schema before writing queries. For "columns": provide the table name in "filter". For "tables"/"procedures": filter is optional (LIKE pattern).

IMPORTANT: Before calling this tool, you MUST confirm which database the user intends to query. If the user has not explicitly stated the target database in their message, ASK them first. Do NOT assume the currently connected database is the intended target.

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": {
      "objectType": "<objectType>"
    },
    "name": "get_schema_info"
  }
}

Input Schema

NameRequiredDescriptionDefault
filterNoFor columns: table name (required). For tables/procedures: optional LIKE pattern.
objectTypeYesType of metadata to retrieve

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.6.0

TDQS

A3.9/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 state 'Read-only', plus a hard pre-call confirmation requirement that an agent would otherwise stumble over. It doesn't describe the shape of returned metadata or limits, so it's not fully exhaustive.

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?

Front-loads the core purpose and the read-only guarantee, then the parameter rules, then the critical precondition. The parameter sentences duplicate the input schema, which is some redundancy, but the IMPORTANT block is well-placed and earns its length.

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 2-parameter, non-destructive introspection tool with no output schema, the description covers purpose, safety, filter semantics, and the target-database precondition adequately. It omits what metadata fields are returned and any pagination/limit behavior, which is a minor gap.

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 100% and the description essentially restates the schema text verbatim ('For columns: provide the table name in "filter". For tables/procedures: filter is optional (LIKE pattern)'). It adds no syntax, cardinality, or edge-case meaning beyond what the schema already documents, so the baseline of 3 applies.

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?

States a specific verb ('Retrieve') and resource ('metadata about tables, columns, or procedures') and enumerates the three object types, so the agent knows exactly what it returns. It does not name the sibling it contrasts with (execute_sql), leaving that differentiation implicit in 'before writing queries'.

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?

'Use this to explore the schema before writing queries' gives clear when-to-use context and implicitly frames the query tools as the alternative. The mandatory precondition ('MUST confirm which database the user intends to query... ASK them first') is unusually explicit and actionable.

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