Skip to main content
Glama

Drupal Code Query

by tech.tresbien

Project profile

project_profile
Read-onlyIdempotent

Answer "what is this contrib project, how big is it, which core versions does it support, what moves with it" for one drupal.org project. Pending change records: project_upgrade_report. Core symbols it calls: list_symbol_users.

  • project: title, type, status, security, installs. installs_by_version: install base per contrib version.

  • dev_branches: each scanned development branch, with installs, core_constraint, core_minors, latest commit date and era. core_constraint: the composer constraint of the newest release on that line, as drupal.org publishes it. The unreleased tip is excluded. core_minors: the minors it admits; a minor counts when any patch satisfies. latest_core_minor: the newest admitted.

  • releases: newest first, up to releases, each with core_compatibility and security. release_count, supported_branches. missing_sections: what the bundle could not fill.

  • related (summary): requires and required_by counts with the top 3, co_installed top 3 or a note, delta_12m per release line ("*" is the total).

  • include=["related"]: related becomes the full report. requires: every dependency, via info_yml or composer, core modules left out. required_by: paged by installs, with count and next_offset; page with dependents and dependents_offset. co_installed: rho, rank, method residual_spearman, or a note.

  • include=["trend"]: trend has months (oldest first), series per release_line aligned with months (null: no count, "*": total), and lines. Each line: installs_now, share, delta_3m, delta_12m, delta_36m, peak, first_seen, last_seen. Counts are drupal.org month-end installs.

  • Unknown project: error. An included section refuses when the bundle predates its view.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
monthsNoWith include trend: months of history, 1 to 120 (default 36), ending at the latest month in the data.
includeNoOptional sections: trend (monthly install series per release line) and related (full requires / required_by / co_installed lists, replacing the related summary).
projectYesdrupal.org project machine name, e.g. webform. The composer name drupal/webform is accepted.
releasesNoReleases to list, newest first, 1 to 30 (default 10). release_count says how many exist.
dependentsNoWith include related: dependents per page in required_by, 1 to 100 (default 20).
dependents_offsetNoWith include related: dependents to skip. Pass required_by.next_offset from the previous call.

Schema Changelog

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

  1. Changed2 schema fields changed
    • changedInput schema / properties / dependents_offset / description
      Previous value: -"With include related: dependents to skip; pass required_by.next_offset from the previous call."New value: +"With include related: dependents to skip. Pass required_by.next_offset from the previous call."
    • changedInput schema / properties / project / description
      Previous value: -"drupal.org project machine name, e.g. webform; the composer name drupal/webform is accepted."New value: +"drupal.org project machine name, e.g. webform. The composer name drupal/webform is accepted."
  2. Changed5 schema fields changed
    • addedInput schema / properties / dependents
      Added value: +{
+  "description": "With include related: dependents per page in required_by, 1 to 100 (default 20).",
+  "type": "integer"
+}
    • addedInput schema / properties / dependents_offset
      Added value: +{
+  "description": "With include related: dependents to skip; pass required_by.next_offset from the previous call.",
+  "type": "integer"
+}
    • addedInput schema / properties / include
      Added value: +{
+  "description": "Optional sections: trend (monthly install series per release line) and related (full requires / required_by / co_installed lists, replacing the related summary).",
+  "items": {
+    "type": "string"
+  },
+  "type": [
+    "null",
+    "array"
+  ]
+}
    • addedInput schema / properties / months
      Added value: +{
+  "description": "With include trend: months of history, 1 to 120 (default 36), ending at the latest month in the data.",
+  "type": "integer"
+}
    • changedInput schema / properties / project / description
      Previous value: -"drupal.org project machine name, e.g. webform."New value: +"drupal.org project machine name, e.g. webform; the composer name drupal/webform is accepted."
  3. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -{
-  "additionalProperties": false,
-  "properties": {
-    "dev_branches": {
-      "items": {
-        "additionalProperties": false,
-        "properties": {
-          "branch": {
-            "type": "string"
-          },
-          "core_constraint": {
-            "type": "string"
-          },
-          "core_minors": {
-            "items": {
-              "type": "string"
-            },
-            "type": [
-              "null",
-              "array"
-            ]
-          },
-          "era": {
-            "type": "string"
-          },
-          "installs": {
-            "type": "integer"
-          },
-          "latest_commit_date": {
-            "type": "string"
-          }
-        },
-        "required": [
-          "branch",
-          "installs",
-          "core_minors"
-        ],
-        "type": "object"
-      },
-      "type": [
-        "null",
-        "array"
-      ]
-    },
-    "installs_by_version": {
-      "items": {
-        "additionalProperties": false,
-        "properties": {
-          "installs": {
-            "type": "integer"
-          },
-          "version": {
-            "type": "string"
-          }
-        },
-        "required": [
-          "version",
-          "installs"
-        ],
-        "type": "object"
-      },
-      "type": [
-        "null",
-        "array"
-      ]
-    },
-    "latest_core_minor": {
-      "type": "string"
-    },
-    "missing_sections": {
-      "items": {
-        "type": "string"
-      },
-      "type": [
-        "null",
-        "array"
-      ]
-    },
-    "project": {
-      "additionalProperties": false,
-      "properties": {
-        "installs": {
-          "type": "integer"
-        },
-        "machine_name": {
-          "type": "string"
-        },
-        "security": {
-          "type": "string"
-        },
-        "status": {
-          "type": "string"
-        },
-        "title": {
-          "type": "string"
-        },
-        "type": {
-          "type": "string"
-        }
-      },
-      "required": [
-        "machine_name",
-        "installs"
-      ],
-      "type": "object"
-    },
-    "release_count": {
-      "type": "integer"
-    },
-    "releases": {
-      "items": {
-        "additionalProperties": false,
-        "properties": {
-          "core_compatibility": {
-            "type": "string"
-          },
-          "date": {
-            "type": "string"
-          },
-          "security": {
-            "type": "boolean"
-          },
-          "status": {
-            "type": "string"
-          },
-          "version": {
-            "type": "string"
-          }
-        },
-        "required": [
-          "version",
-          "security"
-        ],
-        "type": "object"
-      },
-      "type": [
-        "null",
-        "array"
-      ]
-    },
-    "supported_branches": {
-      "items": {
-        "additionalProperties": false,
-        "properties": {
-          "branch": {
-            "type": "string"
-          },
-          "installs": {
-            "type": "integer"
-          }
-        },
-        "required": [
-          "branch",
-          "installs"
-        ],
-        "type": "object"
-      },
-      "type": [
-        "null",
-        "array"
-      ]
-    }
-  },
-  "required": [
-    "project",
-    "installs_by_version",
-    "dev_branches",
-    "releases",
-    "release_count",
-    "supported_branches"
-  ],
-  "type": "object"
-}New value: +null
  4. Added

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, so the safety profile is covered. The description adds substantial behavioral detail: unknown projects produce an error, included sections can refuse when the bundle predates the view, the unreleased tip is excluded from dev branches, and counts are drupal.org month-end installs. No contradiction with annotations exists.

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 purpose is front-loaded in the first sentence, followed by dense but organized bullet sections with no filler. Though long, the length is justified by the number of output sections, parameter-dependent behaviors, and edge cases that need explanation.

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?

Despite lacking an output schema, the description inventories all returned sections, defines core_constraint and core_minors semantics, covers error and limitation behavior, and names sibling tools for adjacent data needs. An agent can predict both call semantics and result interpretation without further documentation.

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 description coverage is 100%, so the baseline is 3. The description adds meaningful beyond-schema behavior for the include parameter: 'related' becomes the full report, required_by uses paging with next_offset, and 'trend' aligns series to months with null and '*' conventions. This is enough to move above baseline.

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 a specific purpose: answer 'what is this contrib project, how big is it, which core versions does it support, what moves with it' for one drupal.org project. It clearly names the resource scope ('one drupal.org project') and points to sibling tools for adjacent concerns such as pending change records and core symbols. This makes it distinguishable from list_projects and other siblings.

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

Usage Guidelines4/5

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

The description gives clear context for when to use the tool and names alternatives for adjacent data needs: 'Pending change records: project_upgrade_report. Core symbols it calls: list_symbol_users.' It also explains optional include modes and what they replace. It does not state an explicit global 'when not to use this tool' rule, but the context is strong enough for an agent to route correctly.

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