MCP Firebird

List Stored Procedures

list-procedures

Read-onlyIdempotent

Retrieve all stored procedures from a Firebird database, including input and output parameters, to support database analysis and management.

Instructions

Lists all stored procedures in the database with input and output parameter information

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

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.

Changed2 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"

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": {
+        "procedures": {
+          "items": {
+            "additionalProperties": false,
+            "properties": {
+              "description": {
+                "$ref": "#/$defs/__schema0"
+              },
+              "inputParams": {
+                "type": "number"
+              },
+              "name": {
+                "type": "string"
+              },
+              "outputParams": {
+                "type": "number"
+              },
+              "source": {
+                "$ref": "#/$defs/__schema0"
+              },
+              "validBlr": {
+                "type": "boolean"
+              }
+            },
+            "required": [
+              "name",
+              "inputParams",
+              "outputParams",
+              "source",
+              "validBlr"
+            ],
+            "type": "object"
+          },
+          "type": "array"
+        },
+        "totalProcedures": {
+          "type": "number"
+        }
+      },
+      "required": [
+        "totalProcedures",
+        "procedures"
+      ],
+      "type": "object"
+    },
+    "success": {
+      "description": "False for tool failures, including partially failed batches",
+      "type": "boolean"
+    }
+  },
+  "required": [
+    "success"
+  ],
+  "type": "object"
+}

Addedv2.8.1Jun 29, 2026

TDQS

A3.6/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's only added behavioral context is that output includes parameter information, which is modest value on top of the existing output schema.

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

Conciseness4/5

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

A single, front-loaded sentence with no filler or restatement of the tool name. It is appropriately sized for a zero-parameter listing tool, though it stops short of any additional scoping detail.

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?

With an output schema present, the description need not explain return values, and with no parameters there are no inputs to document. The definition covers scope and output content adequately, though it could note whether results are filtered or scoped in any way.

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 takes zero parameters, so there is nothing for the description to disambiguate; the baseline of 4 applies. Schema coverage is also 100%, leaving no semantic gap.

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 ('Lists all stored procedures') plus what the result contains (input and output parameter info). It does not explicitly differentiate itself from the sibling describe-procedure, which returns detail for a single procedure, but the 'all' scope makes the distinction reasonably inferable.

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?

The listing intent is implied by the name and description, but there is no explicit when-to-use guidance and no mention of the natural alternative (describe-procedure) for inspecting a single procedure in depth. A reader gets the gist without being routed between siblings.

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