MCP Firebird

Describe Trigger

describe-trigger

Read-onlyIdempotent

Retrieve detailed information about a specific trigger in a Firebird database, including source code, type, sequence, and status. Provide the trigger name to view its definition and behavior.

Instructions

Gets detailed information about a specific trigger, including its source code, type, sequence, and status

Input Schema

TableJSON Schema

Name	Required	Description	Default
`triggerName`	Yes	Name of the trigger to describe

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.

Changed3 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
```

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": {
+        "description": {
+          "$ref": "#/$defs/__schema0"
+        },
+        "inactive": {
+          "type": "boolean"
+        },
+        "name": {
+          "type": "string"
+        },
+        "sequence": {
+          "type": "number"
+        },
+        "source": {
+          "$ref": "#/$defs/__schema0"
+        },
+        "tableName": {
+          "type": "string"
+        },
+        "triggerType": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "name",
+        "tableName",
+        "triggerType",
+        "sequence",
+        "inactive",
+        "source"
+      ],
+      "type": "object"
+    },
+    "success": {
+      "description": "False for tool failures, including partially failed batches",
+      "type": "boolean"
+    }
+  },
+  "required": [
+    "success"
+  ],
+  "type": "object"
+}

Changed1 schema field changedv2.9.0Aug 20, 2026
- changedInput schema / properties / triggerName / description
```
Previous value: -"Nombre del trigger a describir"New value: +"Name of the trigger to describe"
```
Addedv2.8.1Jun 29, 2026

TDQS

A3.5/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is fully covered without the description. The description adds useful content disclosure (source code, type, sequence, status), though with an output schema present that detail is somewhat redundant; no pagination, permissions, or error behavior is discussed.

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?

One sentence, front-loaded with the verb and payload description, with no filler. It could arguably be trimmed since the listed fields overlap with the output schema, but every clause is informative.

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 only one required parameter at full schema coverage, rich annotations, and an output schema handling return values, the description supplies everything an agent needs to invoke the tool correctly. The only missing element is routing guidance relative to the many sibling list/describe tools.

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?

There is a single parameter with 100% schema description coverage, so the schema fully documents 'triggerName'. The description adds no syntax, naming convention, or case-sensitivity guidance beyond what the schema states, which is the expected baseline here.

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?

Specific verb ('Gets detailed information') plus a precise resource ('a specific trigger'), and it enumerates the content returned (source code, type, sequence, status). It does not, however, distinguish itself from siblings like list-triggers or get-table-triggers, so an agent must infer that 'a specific trigger' implies single-item lookup.

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 phrase 'a specific trigger' suggests this is the single-item counterpart to list-triggers, but no alternative tool is named and no condition for choosing between them is stated. Adequate minimum viability, no explicit when/when-not guidance.

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