Skip to main content
Glama
Sign In
CoraDB MCP Server

CoraDB MCP Server

Official
by apsisware
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Run CoraDB SELECT statements

execute_select
Read-only

Run one or more SELECT statements against CoraDB to retrieve result columns and rows for relational SQL or graph queries, with non-SELECT statements refused and nothing committed.

Instructions

Run one SELECT, or several separated by ;, and return the columns (name, type, precision, scale) and rows exactly as the engine returns them. Works for relational SQL and graph queries (SELECT … FROM MATCH …). Each statement is compiled first and refused unless it is a SELECT; nothing is ever committed. Statements run in order and the first error stops the script.

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

Input Schema

NameRequiredDescriptionDefault
sqlYesOne or more SELECT statements separated by ;.
hostNoCoraDB broker host. Default: localhost.
portNoCoraDB broker port. Default: 33000.
userNoDatabase user. Default: dba.
paramsNoValues for the ? placeholders of a single statement, in order.
maxRowsNoMost rows to return per SELECT (default 200, at most 5000). totalRows still reports the full count.
databaseYesThe database to open.
passwordNoPassword of that user. Default: empty.
timeoutMsNoTime limit for the whole call, in milliseconds (default 120000, at most 600000). When it runs out the running statement is cancelled on the server, the rest are skipped and everything is rolled back.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.1/5.0
Behavior5/5

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

Goes well past the annotations: statements are compiled up-front and rejected unless they are SELECTs, nothing is committed, statements execute in order, and the first error aborts the remainder. It also discloses the exact return shape (column name, type, precision, scale plus rows as the engine emits them), which the missing output schema would otherwise leave unknown.

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?

Four sentences, each carrying distinct information: return shape first, supported dialects second, safety/validation third, execution and error ordering last. No repetition of the tool name or title and no filler.

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

Completeness5/5

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

With nine parameters and no output schema, the description compensates by describing the result set layout, the multi-statement execution model, error behavior, and the no-commit guarantee. Connection details and limits live in the schema, so nothing material is left unexplained for an agent to call it correctly.

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%, so every parameter including maxRows, timeoutMs, and params placeholders is already documented in structured form. The description adds only the semicolon-separated multi-statement convention for sql; it does not explain the ? placeholder binding or the row-limit interaction beyond what the schema states, so the 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?

States a specific verb and resource ('Run one SELECT... return the columns and rows') and names the scope (relational SQL plus graph SELECT…FROM MATCH). The read-only restriction ('refused unless it is a SELECT') implicitly separates it from a general execute_sql sibling, but no sibling is named explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives useful context — multi-statement scripts are allowed, graph queries are supported — so the agent can infer when this applies. It never says when to prefer execute_sql, explain_query, or describe_schema instead, leaving the routing decision to be inferred from the read-only constraint.

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