Skip to main content
Glama

Drupal Code Query

by tech.tresbien

Contrib classes extending a core class

list_class_relations
Read-onlyIdempotent

List the contrib classes that extend, implement or use a core class, interface or trait, one row per edge with file and line, paged. Example: "who subclasses FormBase". Call-site counts: list_symbol_users. The symbol's status: lookup_core_symbol.

  • target: with or without the leading backslash. An unknown target is refused with a pointer at lookup_core_symbol; a fragment there lists candidates. rel_kind: one of extends, implements, uses_trait. project: one machine name.

  • Development branches only. edge_count: every edge. project_count: projects. count: edges after the per_project cap. project_edges on each row: the project's full count. per_project=50 with project= lists one project in full.

  • Rows are ordered by project installs, project, source_fqn. Each row: project, branch, installs, source_fqn, rel_kind, file, line, project_edges. limit ≤ 100. next_offset is absent on the last page.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoRows per page, 1 to 100 (default 50).
offsetNoSkip this many rows in the same ranked order. Pass the previous page's next_offset.
targetYesThe core class, interface or trait, with or without the leading backslash: Drupal\Core\Form\FormBase.
projectNoRestrict to one project machine name.
rel_kindNoextends, implements, or uses_trait; any when absent.
per_projectNoEdges shown per project on a page, 1 to 50 (default 3). Each row has project_edges, the project's full count.

Schema Changelog

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

  1. Changed2 schema fields changed
    • changedInput schema / properties / offset / description
      Previous value: -"Skip this many rows in the same ranked order; pass the previous page's next_offset."New value: +"Skip this many rows in the same ranked order. Pass the previous page's next_offset."
    • changedInput schema / properties / per_project / description
      Previous value: -"Edges shown per project on a page, 1 to 50 (default 3), so one project with many subclasses does not fill the page; each row carries project_edges, the project's full count."New value: +"Edges shown per project on a page, 1 to 50 (default 3). Each row has project_edges, the project's full count."
  2. Changed1 schema field changed
    • changedInput schema / properties / target / description
      Previous value: -"The core class, interface or trait, with or without the leading backslash: Drupal\\\\Core\\\\Form\\\\FormBase."New value: +"The core class, interface or trait, with or without the leading backslash: Drupal\\Core\\Form\\FormBase."
  3. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -{
-  "additionalProperties": false,
-  "properties": {
-    "count": {
-      "type": "integer"
-    },
-    "edge_count": {
-      "type": "integer"
-    },
-    "next_offset": {
-      "type": "integer"
-    },
-    "project_count": {
-      "type": "integer"
-    },
-    "ranked_by": {
-      "type": "string"
-    },
-    "rows": {
-      "items": {
-        "additionalProperties": false,
-        "properties": {
-          "branch": {
-            "type": "string"
-          },
-          "file": {
-            "type": "string"
-          },
-          "installs": {
-            "type": "integer"
-          },
-          "line": {
-            "type": "integer"
-          },
-          "project": {
-            "type": "string"
-          },
-          "project_edges": {
-            "type": "integer"
-          },
-          "rel_kind": {
-            "type": "string"
-          },
-          "source_fqn": {
-            "type": "string"
-          }
-        },
-        "required": [
-          "project",
-          "branch",
-          "installs",
-          "source_fqn",
-          "rel_kind",
-          "file",
-          "line",
-          "project_edges"
-        ],
-        "type": "object"
-      },
-      "type": [
-        "null",
-        "array"
-      ]
-    },
-    "target": {
-      "type": "string"
-    }
-  },
-  "required": [
-    "target",
-    "edge_count",
-    "project_count",
-    "count",
-    "rows",
-    "ranked_by"
-  ],
-  "type": "object"
-}New value: +null
  4. Changed5 schema fields changed
    • addedInput schema / properties / per_project
      Added value: +{
+  "description": "Edges shown per project on a page, 1 to 50 (default 3), so one project with many subclasses does not fill the page; each row carries project_edges, the project's full count.",
+  "type": "integer"
+}
    • addedOutput schema / properties / edge_count
      Added value: +{
+  "type": "integer"
+}
    • addedOutput schema / properties / rows / items / properties / project_edges
      Added value: +{
+  "type": "integer"
+}
    • changedOutput schema / properties / rows / items / required
      Previous value: -[
-  "project",
-  "branch",
-  "installs",
-  "source_fqn",
-  "rel_kind",
-  "file",
-  "line"
-]New value: +[
+  "project",
+  "branch",
+  "installs",
+  "source_fqn",
+  "rel_kind",
+  "file",
+  "line",
+  "project_edges"
+]
    • changedOutput schema / required
      Previous value: -[
-  "target",
-  "project_count",
-  "count",
-  "rows",
-  "ranked_by"
-]New value: +[
+  "target",
+  "edge_count",
+  "project_count",
+  "count",
+  "rows",
+  "ranked_by"
+]
  5. Changed1 schema field changed
    • changedOutput schema / required
      Previous value: -[
-  "target",
-  "count",
-  "project_count",
-  "rows",
-  "ranked_by"
-]New value: +[
+  "target",
+  "project_count",
+  "count",
+  "rows",
+  "ranked_by"
+]
  6. Added

TDQS

A5/5.0
Behavior5/5

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

Annotations already mark the tool read-only and idempotent, but the description adds important runtime behavior: development branches only, unknown targets are refused with a pointer to lookup_core_symbol, per-project capping semantics, ordering, and next_offset absence on the last page. There is no contradiction with the annotations.

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 front-loaded with the primary purpose and an example, then moves into dense but purposeful reference details. Every sentence adds information needed to call the tool correctly; there is no filler or repetition of the title.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/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 fully specifies the row fields, ordering, pagination behavior, and error handling. The inclusion of sibling-tool routing and parameter edge cases makes the tool self-sufficient for an agent deciding whether and how to invoke it.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Although the input schema covers all parameters, the description adds meaning beyond it: the target may include or omit the leading backslash, rel_kind values are clarified, per_project controls the capping while project_edges gives the full count, and limit/offset/next_offset behavior is explained. This is substantial navigational guidance for constructing queries.

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 states exactly what the tool does: lists contrib classes that extend, implement, or use a core class/interface/trait, with one row per edge including file and line, paged. The concrete example "who subclasses FormBase" and the naming of related sibling tools remove ambiguity.

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?

It explicitly routes the agent to alternatives: call-site counts should use list_symbol_users, and symbol-status or candidate lookup should use lookup_core_symbol. It also explains the unknown-target refusal path, making the choice between tools clear.

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