MCP Firebird

Get Table Data

get-table-data

Read-onlyIdempotent

Retrieve data from a Firebird table using filters, ordering, and pagination to inspect or analyze specific rows.

Instructions

Retrieves data from a specific table with optional filtering, pagination, and ordering.

Input Schema

TableJSON Schema

Name	Required	Description
`skip`	No	Number of rows to skip
`first`	No	Number of rows to retrieve (maximum: 1000)
`filters`	No	Structured filters; values are always parameterized
`orderBy`	No
`tableName`	Yes	Name of the table to retrieve data from

Output Schema

TableJSON Schema

Name	Required	Description
`error`	No	Failure information; present when success is false
`result`	No	The legacy JSON payload; present for completed operations and partial batches
`success`	Yes	False for tool failures, including partially failed batches

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedv2.12.0Oct 7, 2026

changedInput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

removedInput schema / additionalProperties
```
Removed value: -false
```
removedInput schema / properties / filters / items / additionalProperties
```
Removed value: -false
```
removedInput schema / properties / orderBy / items / additionalProperties
```
Removed value: -false
```

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$defs": {
+    "__schema0": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "number"
+        },
+        {
+          "type": "boolean"
+        },
+        {
+          "type": "null"
+        },
+        {
+          "items": {
+            "$ref": "#/$defs/__schema0"
+          },
+          "type": "array"
+        },
+        {
+          "additionalProperties": {
+            "$ref": "#/$defs/__schema0"
+          },
+          "propertyNames": {
+            "type": "string"
+          },
+          "type": "object"
+        }
+      ]
+    },
+    "__schema1": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "number"
+        },
+        {
+          "type": "boolean"
+        },
+        {
+          "type": "null"
+        },
+        {
+          "items": {
+            "$ref": "#/$defs/__schema1"
+          },
+          "type": "array"
+        },
+        {
+          "additionalProperties": {
+            "$ref": "#/$defs/__schema1"
+          },
+          "propertyNames": {
+            "type": "string"
+          },
+          "type": "object"
+        }
+      ]
+    }
+  },
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "additionalProperties": false,
+  "properties": {
+    "error": {
+      "additionalProperties": false,
+      "description": "Failure information; present when success is false",
+      "properties": {
+        "details": {
+          "additionalProperties": {
+            "$ref": "#/$defs/__schema1"
+          },
+          "propertyNames": {
+            "type": "string"
+          },
+          "type": "object"
+        },
+        "message": {
+          "type": "string"
+        },
+        "type": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "message",
+        "type"
+      ],
+      "type": "object"
+    },
+    "result": {
+      "additionalProperties": false,
+      "description": "The legacy JSON payload; present for completed operations and partial batches",
+      "properties": {
+        "data": {
+          "items": {
+            "additionalProperties": {
+              "$ref": "#/$defs/__schema0"
+            },
+            "propertyNames": {
+              "type": "string"
+            },
+            "type": "object"
+          },
+          "type": "array"
+        },
+        "rowCount": {
+          "type": "number"
+        },
+        "tableName": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "tableName",
+        "rowCount",
+        "data"
+      ],
+      "type": "object"
+    },
+    "success": {
+      "description": "False for tool failures, including partially failed batches",
+      "type": "boolean"
+    }
+  },
+  "required": [
+    "success"
+  ],
+  "type": "object"
+}

Changed12 schema fields changedv2.9.3Sep 1, 2026

addedInput schema / properties / filters

Added value: +{
+  "description": "Structured filters; values are always parameterized",
+  "items": {
+    "additionalProperties": false,
+    "properties": {
+      "column": {
+        "minLength": 1,
+        "type": "string"
+      },
+      "operator": {
+        "enum": [
+          "eq",
+          "ne",
+          "gt",
+          "gte",
+          "lt",
+          "lte",
+          "like",
+          "in",
+          "isNull",
+          "isNotNull"
+        ],
+        "type": "string"
+      },
+      "value": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "type": "number"
+          },
+          {
+            "type": "boolean"
+          },
+          {
+            "type": "null"
+          },
+          {
+            "items": {
+              "type": [
+                "string",
+                "number",
+                "boolean"
+              ]
+            },
+            "maxItems": 100,
+            "minItems": 1,
+            "type": "array"
+          }
+        ]
+      }
+    },
+    "required": [
+      "column",
+      "operator"
+    ],
+    "type": "object"
+  },
+  "maxItems": 20,
+  "type": "array"
+}

addedInput schema / properties / first / default
```
Added value: +100
```

changedInput schema / properties / first / description

Previous value: -"Number of rows to retrieve (FIRST clause in Firebird)"New value: +"Number of rows to retrieve (maximum: 1000)"

addedInput schema / properties / first / maximum
```
Added value: +1000
```

removedInput schema / properties / orderBy / description

Removed value: -"Optional ORDER BY clause (without the ORDER BY keyword)"

addedInput schema / properties / orderBy / items

Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "column": {
+      "minLength": 1,
+      "type": "string"
+    },
+    "direction": {
+      "default": "ASC",
+      "enum": [
+        "ASC",
+        "DESC"
+      ],
+      "type": "string"
+    }
+  },
+  "required": [
+    "column"
+  ],
+  "type": "object"
+}

addedInput schema / properties / orderBy / maxItems
```
Added value: +10
```
changedInput schema / properties / orderBy / type
```
Previous value: -"string"New value: +"array"
```
addedInput schema / properties / skip / default
```
Added value: +0
```

changedInput schema / properties / skip / description

Previous value: -"Number of rows to skip (SKIP clause in Firebird)"New value: +"Number of rows to skip"

addedInput schema / properties / skip / maximum
```
Added value: +1000000
```

removedInput schema / properties / where

Removed value: -{
-  "description": "Optional WHERE clause (without the WHERE keyword)",
-  "type": "string"
-}

Addedv1.0.0Jan 2, 2026

TDQS

B3.3/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered by structured data. The description adds only that filtering/pagination/ordering are optional; it does not disclose the 1000-row cap, default page size, or how filters combine, which would have been genuinely additive over the annotations.

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?

A single front-loaded sentence with no filler; the verb, resource, and optional capabilities are all stated immediately and nothing is repeated.

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?

An output schema exists, so return values need no explanation, and annotations cover the safety profile. What is missing is any routing between this tool and execute-query for ad-hoc versus table-scoped retrieval, which matters given the crowded sibling set.

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 80%, so the schema already documents skip, first, filters, and tableName, including the 1000-row maximum. The description names the three parameter families at a high level but adds no syntax, operator, or ordering details beyond what the schema provides, 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 ('Retrieves data from a specific table') plus the three capability areas (filtering, pagination, ordering). However, it never distinguishes itself from the sibling execute-query, which appears to serve a similar data-retrieval purpose, so the agent must infer the boundary.

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?

No when-to-use guidance, no exclusions, and no mention of the obvious alternative (execute-query) despite the sibling list containing a general query tool. The agent gets a description of what the tool does but nothing about when to prefer it.

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