Skip to main content
Glama
Sign In
CoraDB MCP Server

CoraDB MCP Server

Official
by apsisware
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

CoraDB connection info

connection_info
Read-only

Checks CoraDB connectivity by logging in and reporting the login used, engine version, and server settings without exposing the password.

Instructions

Log in to a CoraDB database and report the login used (never the password), the engine version and this server's settings. Use it to check that a database is reachable with a given login.

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": {
      "database": "<database>"
    },
    "name": "connection_info"
  }
}

Input Schema

NameRequiredDescriptionDefault
hostNoCoraDB broker host. Default: localhost.
portNoCoraDB broker port. Default: 33000.
userNoDatabase user. Default: dba.
databaseYesThe database to open.
passwordNoPassword of that user. Default: empty.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4/5.0
Behavior4/5

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

Annotations only declare readOnlyHint and openWorldHint; the description adds that authentication is required and, importantly, that the password is never echoed back. It also discloses the shape of the result (login, engine version, server settings). It does not describe failure behavior when credentials are wrong, which is the main remaining gap.

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?

Two sentences, front-loaded with the action and its outputs, then the usage condition. Nothing is redundant or restated from the schema.

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 five-parameter connectivity-check tool with no output schema, the description supplies the returned fields and the security caveat, which is most of what an agent needs. Only error/negative-path behavior is left unstated.

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%, with defaults for host, port, user, and password already documented per-parameter. The description mentions 'a given login' but adds no syntax, format, or precedence detail beyond the schema, so baseline 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?

The description names a concrete action ('Log in to a CoraDB database') and enumerates what it reports: the login used, engine version, and server settings. That distinguishes it functionally from the execute_*/describe_schema siblings, though it never names or contrasts them explicitly.

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?

It gives a clear selection rule: 'Use it to check that a database is reachable with a given login.' There are no explicit exclusions (e.g., 'do not use for listing databases'), but the condition for choosing this over the query/schema tools is unambiguous.

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