Skip to main content
Glama
Sign In
mcp-bd-readonly

mcp-bd-readonly

by noemartinezoptima
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

list_tables

Lists all tables in a specified schema, defaulting to 'back'. Use it to inspect available tables in a read-only MySQL inventory and invoicing database.

Instructions

Lista las tablas de un esquema (default 'back').

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
schemaNoback

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden, yet it only implies a read operation via 'Lista'. It says nothing about return format, pagination, permissions, or the failure mode when an unknown schema is passed.

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?

A single compact sentence with no waste and the key information front-loaded. It is appropriately sized for a simple listing tool, though slightly terse.

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 one-parameter read tool this is close to minimally viable, but with no annotations, no output schema, and 0% schema coverage, the description should say more about what is returned and how it relates to sibling tools.

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 0%, so the description must compensate. It identifies the param's meaning (which schema's tables) and its default 'back', but the default is already declared in the schema, so the added value is marginal.

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 and resource ('Lista las tablas de un esquema'), so an agent knows exactly what it returns. It does not explicitly differentiate itself from siblings like list_databases or describe_table, but the resource is distinct enough to be inferred.

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?

The description gives no guidance on when to choose this tool over list_databases or describe_table, nor any preconditions for use. The only contextual hint is the default schema name, which is not usage guidance.

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