Skip to main content
Glama
andreadecorte

GABI MCP Server

by andreadecorte
OverviewSchemaRelated ServersScoreDiscussions
Python
Remote

get_db_name

Retrieve the name of the currently active database to verify connection status and ensure queries target the correct data source.

Instructions

Get the name of the current database.

Args:

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • gabi.py:66-72 (handler)
    The handler function for the 'get_db_name' tool. It is decorated with @mcp.tool() which registers it as an MCP tool. The function makes a GET request to the GABI endpoint '/dbname' to retrieve the current database name and returns it as a string.
    @mcp.tool()
async def get_db_name() -> str:
    """Get the name of the current database.

    Args:
    """
    return await make_gabi_get_request(build_gabi_url("/dbname"))

Tool Definition Quality

C2.9/5.0
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states what the tool does but doesn't describe any behavioral traits such as whether it's read-only, requires authentication, has rate limits, or what the return format looks like. This is a significant gap for a tool with zero annotation coverage.

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

Conciseness3/5

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

The description is concise with a single clear sentence, but the 'Args:' section is empty and adds no value, creating unnecessary structure. The core description is efficient, but the formatting could be cleaner.

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

Completeness2/5

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

Given the lack of annotations and output schema, the description is incomplete. It explains the basic purpose but doesn't cover behavioral aspects like return format, error conditions, or usage context relative to the sibling tool. For a tool with no structured metadata, more detail is needed.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool has 0 parameters, and the schema description coverage is 100% (though trivial since there are no parameters). The description doesn't need to add parameter semantics, so it meets the baseline expectation for a parameterless tool.

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 clearly states the tool's purpose with a specific verb ('Get') and resource ('name of the current database'), making it immediately understandable. However, it doesn't explicitly differentiate from its sibling tool 'get_query_result', which appears to serve a different function (querying vs. metadata retrieval).

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 provides no guidance on when to use this tool versus alternatives or in what context it's appropriate. It doesn't mention the sibling tool 'get_query_result' or any other tools, leaving the agent without usage context.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/andreadecorte/gabi-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server