Skip to main content
Glama

Drupal Code Query

by tech.tresbien
OverviewDiscussionsAdmin

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).

  • member_of: how many roots pull this project in (count), and up to 10 {root, depth}, shallowest and alphabetical first.

  • 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.

  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.4/5.0
Behavior5/5

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

The description goes well beyond the readOnly/idempotent annotations, documenting error behavior for unknown projects, the refusal of included sections when the bundle predates the view, data sources, exclusions like the unreleased tip, and count semantics. This gives an agent a precise model of side effects and limitations.

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 long but organized into tight bullets that each carry specific output facts; no filler. Some definitions, such as core_constraint, are repeated between bullets, and the cross-reference line at the top adds only marginal value, so it is not perfect.

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 carries the full burden of explaining return shape, and it does so thoroughly: every return section, parameter effect, paging mechanism, and error/refusal case is covered. An agent has enough to invoke correctly and interpret results.

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?

All six parameters are already described in the schema (100% coverage), so the baseline is 3. The description adds value by explaining how include modifies the related section, how dependents_offset paginates via next_offset, and how releases/months interact with output, so it earns a 4.

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 quoted purpose statement naming the exact questions the tool answers for one drupal.org project, then enumerates returned sections. It is a specific verb+resource and distinguishes itself from siblings by explicitly naming project_upgrade_report and list_symbol_users as related but separate concerns.

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?

The description implies use when a one-project profile is needed, but it never states when to choose this over siblings or when not to use it. The cross-references to project_upgrade_report and list_symbol_users hint at boundaries without giving explicit selection criteria.

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
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources