Skip to main content
Glama
PuroDelphi

MCP Firebird

by PuroDelphi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

get-table-triggers

get-table-triggers
Read-onlyIdempotent

Retrieve all triggers defined on a specific Firebird table, including source, type, sequence, and active state.

Instructions

Returns only the triggers associated with a table, including source, description, sequence, type, and active state.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tableNameYesName of the table whose relational metadata should be returned

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
errorNoFailure information; present when success is false
resultNoThe legacy JSON payload; present for completed operations and partial batches
successYesFalse for tool failures, including partially failed batches

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv2.12.0
    • 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
    • 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"
+        }
+      ]
+    }
+  },
+  "$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/__schema0"
+          },
+          "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": {
+        "tableName": {
+          "type": "string"
+        },
+        "triggers": {
+          "items": {
+            "additionalProperties": false,
+            "properties": {
+              "description": {
+                "type": "string"
+              },
+              "isActive": {
+                "type": "boolean"
+              },
+              "name": {
+                "type": "string"
+              },
+              "sequence": {
+                "type": [
+                  "number",
+                  "null"
+                ]
+              },
+              "source": {
+                "type": "string"
+              },
+              "type": {
+                "type": [
+                  "number",
+                  "null"
+                ]
+              }
+            },
+            "required": [
+              "isActive",
+              "source"
+            ],
+            "type": "object"
+          },
+          "type": "array"
+        }
+      },
+      "required": [
+        "tableName",
+        "triggers"
+      ],
+      "type": "object"
+    },
+    "success": {
+      "description": "False for tool failures, including partially failed batches",
+      "type": "boolean"
+    }
+  },
+  "required": [
+    "success"
+  ],
+  "type": "object"
+}
  2. Addedv2.10.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, fully covering the safety profile for a read operation. The description adds no behavioral context beyond that (no ordering guarantees, no handling of a missing table), so it neither contradicts nor enriches the structured data.

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?

One sentence, front-loaded with the verb and scope, with no filler. The enumerated return fields are mildly redundant given the output schema, but the sentence is tight and readable.

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 a rich annotation set, a fully documented single parameter, and an output schema, the description only needs to establish purpose and scope, which it does. The one residual gap is not explicitly routing the agent between this tool and the sibling list-triggers/describe-trigger.

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?

The single parameter tableName has 100% schema description coverage, so the schema already documents it fully. The description adds no format or constraint detail beyond identifying the table scope, 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 (returns triggers for a table) and names the returned fields. The word "only" scopes it relative to the sibling list-triggers, but the differentiation is implicit rather than explicit. An agent can mostly tell it apart, though not with the certainty of a named alternative.

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?

Usage is only implied: the table-scoped nature suggests using this when you already know the table, versus list-triggers for a broad listing. No explicit when-to-use, prerequisites, or named alternatives are given, so the agent must infer the choice from the name and scope wording.

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