Skip to main content
Glama

Drupal Code Query

by tech.tresbien

One change record

get_change_record
Read-onlyIdempotent

Return one core change record in full: title, flavour, target version, machine-checkable tracks, linked issues, linked core symbols, and contrib adoption counts. To find records, use list_change_records or the change_record_nids from what_changed. For one symbol's detail, use lookup_core_symbol.

  • flavour: coming-break (an API going away), coming-new-API (an API added), landed-but-still-relevant (shipped), policy-only (no code target, no adoption).

  • Adoption counts contrib development branches only. legacy: still calls the going-away side. migrated: moved to the new side.

  • Returns counts across every affected project plus a ranked head, outstanding first. For one project, use project_upgrade_report; do not raise top_projects.

  • symbols: the core API the record is about. role: from (going away) or to (replacement). Use the fqn with lookup_core_symbol. Empty means the catalog links no symbol; that is common.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nidYesThe change record's drupal.org node id, for example 3581981.
top_projectsNoHow many impacted projects to return in the ranked head. Defaults to 10, capped at 40.

Schema Changelog

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

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -{
-  "additionalProperties": false,
-  "properties": {
-    "computed_at": {
-      "type": [
-        "null",
-        "string"
-      ]
-    },
-    "flavor": {
-      "type": "string"
-    },
-    "impact": {
-      "additionalProperties": false,
-      "properties": {
-        "axis": {
-          "type": "string"
-        },
-        "branches": {
-          "additionalProperties": false,
-          "properties": {
-            "in_flight": {
-              "type": "integer"
-            },
-            "legacy": {
-              "type": "integer"
-            },
-            "migrated": {
-              "type": "integer"
-            }
-          },
-          "required": [
-            "legacy",
-            "in_flight",
-            "migrated"
-          ],
-          "type": "object"
-        },
-        "projects": {
-          "type": "integer"
-        },
-        "projects_outstanding": {
-          "type": "integer"
-        },
-        "top_projects": {
-          "items": {
-            "additionalProperties": false,
-            "properties": {
-              "in_flight": {
-                "type": "integer"
-              },
-              "installs": {
-                "type": "integer"
-              },
-              "legacy": {
-                "type": "integer"
-              },
-              "migrated": {
-                "type": "integer"
-              },
-              "project": {
-                "type": "string"
-              }
-            },
-            "required": [
-              "project",
-              "installs",
-              "legacy",
-              "in_flight",
-              "migrated"
-            ],
-            "type": "object"
-          },
-          "type": [
-            "null",
-            "array"
-          ]
-        }
-      },
-      "required": [
-        "axis",
-        "projects",
-        "projects_outstanding",
-        "branches",
-        "top_projects"
-      ],
-      "type": [
-        "null",
-        "object"
-      ]
-    },
-    "issue_count": {
-      "type": "integer"
-    },
-    "issues": {
-      "items": {
-        "type": "integer"
-      },
-      "type": [
-        "null",
-        "array"
-      ]
-    },
-    "nid": {
-      "type": "integer"
-    },
-    "symbols": {
-      "items": {
-        "additionalProperties": false,
-        "properties": {
-          "fqn": {
-            "type": "string"
-          },
-          "kind": {
-            "type": "string"
-          },
-          "role": {
-            "type": "string"
-          }
-        },
-        "required": [
-          "fqn"
-        ],
-        "type": "object"
-      },
-      "type": [
-        "null",
-        "array"
-      ]
-    },
-    "target_version": {
-      "type": "string"
-    },
-    "title": {
-      "type": "string"
-    },
-    "tracks": {
-      "items": {
-        "additionalProperties": false,
-        "properties": {
-          "index": {
-            "type": "integer"
-          },
-          "kind": {
-            "type": "string"
-          },
-          "ledger": {
-            "type": "string"
-          },
-          "polarity": {
-            "type": "string"
-          }
-        },
-        "required": [
-          "index",
-          "kind",
-          "ledger",
-          "polarity"
-        ],
-        "type": "object"
-      },
-      "type": [
-        "null",
-        "array"
-      ]
-    },
-    "url": {
-      "type": "string"
-    }
-  },
-  "required": [
-    "nid",
-    "title",
-    "flavor",
-    "url",
-    "tracks",
-    "issues",
-    "issue_count",
-    "computed_at"
-  ],
-  "type": "object"
-}New value: +null
  2. Changed1 schema field changed
    • addedOutput schema / properties / symbols
      Added value: +{
+  "items": {
+    "additionalProperties": false,
+    "properties": {
+      "fqn": {
+        "type": "string"
+      },
+      "kind": {
+        "type": "string"
+      },
+      "role": {
+        "type": "string"
+      }
+    },
+    "required": [
+      "fqn"
+    ],
+    "type": "object"
+  },
+  "type": [
+    "null",
+    "array"
+  ]
+}
  3. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Even though readOnlyHint/idempotentHint already signal safe reads, the description adds valuable behavioral context: the flavour taxonomy, the fact that adoption counts only cover contrib development branches, the legacy/migrated meanings, the ranked-head ordering with outstanding first, and the meaning of an empty symbols list. None of this is present in annotations.

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?

The description is well-structured: a front-loaded summary sentence, routing guidance, then concise bullets for flavour, adoption, output shape, and symbols. It is longer than minimal but every bullet earns its place. Minor deduction for the ambiguous 'do not raise top_projects' phrasing.

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 no output schema, the description carries extra responsibility for explaining return semantics, and it mostly succeeds: it lists returned content, explains flavour values, adoption scope, and symbol roles. It does not describe exact JSON shape or possible error conditions, but an agent has enough to invoke the tool correctly. The ambiguity around top_projects keeps this from a 5.

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?

Schema coverage is 100%, so the baseline is 3. The description adds meaning beyond the schema by explaining that top_projects controls the ranked head and that the head is ordered outstanding first, and it connects nid to change_record_nids from what_changed. The phrase 'do not raise top_projects' is slightly cryptic, but overall the description enhances the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a specific verb and resource — 'Return one core change record in full' — and enumerates the contained fields. It also differentiates itself from siblings by pointing to list_change_records for finding records and lookup_core_symbol for a single symbol's detail.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives explicit routing: use list_change_records or what_changed to find records, use lookup_core_symbol for symbol-level detail, and use project_upgrade_report for a single project's upgrade report. This gives an agent clear when-to-use and when-not-to-use guidance.

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

All Drupal Code Query toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.6/5.0
Disambiguation4/5

Tools cluster into related families (change records, symbol usage, patch checks), but descriptions and cross-references clearly separate list vs detail vs diff operations. Some adjacent tools like lookup_core_symbol and list_symbol_users require careful reading, yet their purposes are distinct enough for an agent to select correctly.

Naming Consistency4/5

Most tools follow a clear snake_case verb_noun pattern: list_*, get_*, lookup_*, query_, scan_, search_, reroll_, describe_. A few names like project_profile, subsystem_coupling, and what_changed deviate from verb_noun but remain consistent in style and readable.

Tool Count4/5

At 16 tools, the set is slightly above the typical well-scoped range, but the domain is broad: patch lifecycle, composer scanning, symbol lookup, change records, project profiles, dataset queries, and code search. Each tool covers a distinct query surface, so none feels redundant.

Completeness5/5

The toolkit covers the full read-only analysis lifecycle: scanning composer constraints, checking and re-rolling patches, exploring datasets, looking up core symbols and their users, listing change records, profiling projects, and assessing upgrade readiness. No obvious dead ends or missing operations for its stated purpose.

Resources