Skip to main content
Glama
PuroDelphi

MCP Firebird

by PuroDelphi
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Hybrid

Get Table Data

get-table-data

Retrieve data from any Firebird table with optional filters, pagination, and ordering. Query specific rows by column conditions to get exactly the information needed.

Instructions

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
skipNoNumber of rows to skip
firstNoNumber of rows to retrieve (maximum: 1000)
filtersNoStructured filters; values are always parameterized
orderByNo
tableNameYesName of the table to retrieve data from

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed12 schema fields changedv2.9.3
    • 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"
-}
  2. Addedv1.0.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 burden. It implies a read-only operation, but does not disclose response shape, pagination limits, ordering behavior, permissions, or any side-effect safety beyond the word 'Retrieves'.

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?

The description is a single front-loaded sentence with no redundant wording; every word contributes to stating the core function.

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/output schema and the presence of many closely related sibling tools, the description is too sparse to fully route an agent: it omits usage boundaries, default behavior, and relationship to execute-query or list-tables.

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 most parameters. The description adds only high-level references to filtering, pagination, and ordering, which are evident from the parameter names; it does not enrich the meaning of individual parameters.

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 specific verb ('Retrieves') and resource ('data from a specific table'), and notes optional filtering, pagination, and ordering. It is clear enough to distinguish from most table-metadata siblings, though it does not explicitly call out alternatives like execute-query.

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?

There is no guidance on when to choose this tool over execute-query or other retrieval/query tools. The description implies general data retrieval but provides no exclusion criteria or alternative routing.

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/PuroDelphi/mcpFirebird'

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