Skip to main content
Glama

Drupal Code Query

by tech.tresbien

One core symbol: status and users

lookup_core_symbol
Read-onlyIdempotent

Answer "is this core symbol safe to use, and who still uses it" for one symbol. A name that resolves to nothing returns the catalog entries containing it instead. Every user in pages: list_symbol_users. Changed between versions: what_changed. Code text: search_code.

  • fqn forms: a namespaced name with or without the leading backslash, a bare function or constant name, a prefixed pseudo-symbol, or a fragment. Pseudo-symbols: fn:check_markup, core:hook:preprocess_page, core:library:claro/drupal.shortcut. Fragments: fromRoute, EntityInterface.

  • Resolved (found true): symbol, with status flags. removed: gone. scheduled_removal: still present, @deprecated gives the removal version. deprecated, internal. placeholder: a catalog row no scanner located. audience: contrib, test_support, test or theme. usage: contrib development branches only, from the evidence rollup as of evidence_built_at. It has projects and branches counts, plus top_projects (≤ 30) by install base. change_records: records that touched the symbol, each with nid for get_change_record.

  • Not resolved (found false): count: catalog entries containing the fragment, case-insensitive, public symbols only; kind narrows. candidates: a head of up to candidates entries, each with fqn, kind, subsystem, stamps, projects_using, change_record_nids. Entries starting with the fragment come first, then by projects_using. Call again with one fqn.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
fqnYesCore symbol name, or part of one. A namespaced name with or without the leading backslash (Drupal\Core\Entity\EntityInterface, Drupal\Core\Recipe\RecipeRunner::installModule). A bare function or constant name (check_markup, DRUPAL_DISABLED). A prefixed pseudo-symbol as what_changed reports it (fn:check_markup, core:hook:preprocess_page, core:library:claro/drupal.shortcut). A fragment of 3+ characters (fromRoute), which returns candidates when no symbol has that exact name.
kindNoRestrict candidates to one symbol kind (class, method, function, hook, library, service …).
candidatesNoWhen the name resolves to no symbol: how many catalog entries containing it to return, 1 to 50 (default 10).
top_projectsNoHow many using projects to return in the ranked head. Defaults to 10, capped at 30.

Schema Changelog

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

  1. Changed2 schema fields changed
    • changedInput schema / properties / candidates / description
      Previous value: -"When the name resolves to no symbol: how many catalog names containing it to return, 1 to 50 (default 10)."New value: +"When the name resolves to no symbol: how many catalog entries containing it to return, 1 to 50 (default 10)."
    • changedInput schema / properties / fqn / description
      Previous value: -"Core symbol name, or part of one. Namespaced names with or without the leading backslash (Drupal\\Core\\Entity\\EntityInterface, Drupal\\Core\\Recipe\\RecipeRunner::installModule); a bare function or constant name (check_markup, DRUPAL_DISABLED); a prefixed pseudo-symbol as what_changed reports it (fn:check_markup, core:hook:preprocess_page, core:library:claro/drupal.shortcut); or a fragment of 3+ characters (fromRoute), which returns candidates when no symbol has that exact name."New value: +"Core symbol name, or part of one. A namespaced name with or without the leading backslash (Drupal\\Core\\Entity\\EntityInterface, Drupal\\Core\\Recipe\\RecipeRunner::installModule). A bare function or constant name (check_markup, DRUPAL_DISABLED). A prefixed pseudo-symbol as what_changed reports it (fn:check_markup, core:hook:preprocess_page, core:library:claro/drupal.shortcut). A fragment of 3+ characters (fromRoute), which returns candidates when no symbol has that exact name."
  2. Changed3 schema fields changed
    • addedInput schema / properties / candidates
      Added value: +{
+  "description": "When the name resolves to no symbol: how many catalog names containing it to return, 1 to 50 (default 10).",
+  "type": "integer"
+}
    • changedInput schema / properties / fqn / description
      Previous value: -"Core symbol name. Namespaced names with or without the leading backslash (Drupal\\Core\\Entity\\EntityInterface, Drupal\\Core\\Recipe\\RecipeRunner::installModule); a bare function or constant name (check_markup, DRUPAL_DISABLED); or a prefixed pseudo-symbol as what_changed reports it (fn:check_markup, core:hook:preprocess_page, core:library:claro/drupal.shortcut)."New value: +"Core symbol name, or part of one. Namespaced names with or without the leading backslash (Drupal\\Core\\Entity\\EntityInterface, Drupal\\Core\\Recipe\\RecipeRunner::installModule); a bare function or constant name (check_markup, DRUPAL_DISABLED); a prefixed pseudo-symbol as what_changed reports it (fn:check_markup, core:hook:preprocess_page, core:library:claro/drupal.shortcut); or a fragment of 3+ characters (fromRoute), which returns candidates when no symbol has that exact name."
    • addedInput schema / properties / kind
      Added value: +{
+  "description": "Restrict candidates to one symbol kind (class, method, function, hook, library, service …).",
+  "type": "string"
+}
  3. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -{
-  "additionalProperties": false,
-  "properties": {
-    "change_record_count": {
-      "type": "integer"
-    },
-    "change_records": {
-      "items": {
-        "additionalProperties": false,
-        "properties": {
-          "confidence": {
-            "type": "string"
-          },
-          "flavor": {
-            "type": "string"
-          },
-          "nid": {
-            "type": "integer"
-          },
-          "role": {
-            "type": "string"
-          },
-          "target_version": {
-            "type": "string"
-          },
-          "title": {
-            "type": "string"
-          }
-        },
-        "required": [
-          "nid",
-          "title",
-          "flavor"
-        ],
-        "type": "object"
-      },
-      "type": [
-        "null",
-        "array"
-      ]
-    },
-    "symbol": {
-      "additionalProperties": false,
-      "properties": {
-        "added_in": {
-          "type": "string"
-        },
-        "api_scope": {
-          "type": "string"
-        },
-        "audience": {
-          "type": "string"
-        },
-        "deprecated_in": {
-          "type": "string"
-        },
-        "fqn": {
-          "type": "string"
-        },
-        "internal": {
-          "type": "boolean"
-        },
-        "kind": {
-          "type": "string"
-        },
-        "placeholder": {
-          "type": "boolean"
-        },
-        "removal_in": {
-          "type": "string"
-        },
-        "removal_kind": {
-          "type": "string"
-        },
-        "replacement": {
-          "type": "string"
-        },
-        "source": {
-          "type": "string"
-        },
-        "status": {
-          "items": {
-            "type": "string"
-          },
-          "type": [
-            "null",
-            "array"
-          ]
-        },
-        "subsystem": {
-          "type": "string"
-        }
-      },
-      "required": [
-        "fqn",
-        "kind",
-        "internal",
-        "status"
-      ],
-      "type": "object"
-    },
-    "usage": {
-      "additionalProperties": false,
-      "properties": {
-        "dev_branches": {
-          "additionalProperties": false,
-          "properties": {
-            "branches": {
-              "type": "integer"
-            },
-            "occurrences": {
-              "type": "integer"
-            },
-            "projects": {
-              "type": "integer"
-            }
-          },
-          "required": [
-            "projects",
-            "branches",
-            "occurrences"
-          ],
-          "type": "object"
-        },
-        "evidence_built_at": {
-          "type": "string"
-        },
-        "note": {
-          "type": "string"
-        },
-        "release_tags": {
-          "additionalProperties": false,
-          "properties": {
-            "branches": {
-              "type": "integer"
-            },
-            "occurrences": {
-              "type": "integer"
-            },
-            "projects": {
-              "type": "integer"
-            }
-          },
-          "required": [
-            "projects",
-            "branches",
-            "occurrences"
-          ],
-          "type": "object"
-        },
-        "top_projects": {
-          "items": {
-            "additionalProperties": false,
-            "properties": {
-              "branches": {
-                "type": "integer"
-              },
-              "files": {
-                "type": "integer"
-              },
-              "installs": {
-                "type": "integer"
-              },
-              "occurrences": {
-                "type": "integer"
-              },
-              "project": {
-                "type": "string"
-              }
-            },
-            "required": [
-              "project",
-              "branches",
-              "files",
-              "occurrences",
-              "installs"
-            ],
-            "type": "object"
-          },
-          "type": [
-            "null",
-            "array"
-          ]
-        }
-      },
-      "required": [
-        "dev_branches",
-        "release_tags",
-        "top_projects"
-      ],
-      "type": [
-        "null",
-        "object"
-      ]
-    }
-  },
-  "required": [
-    "symbol",
-    "change_records",
-    "change_record_count"
-  ],
-  "type": "object"
-}New value: +null
  4. Changed1 schema field changed
    • addedOutput schema / properties / symbol / properties / removal_kind
      Added value: +{
+  "type": "string"
+}
  5. Changed1 schema field changed
    • addedOutput schema / properties / usage / properties / evidence_built_at
      Added value: +{
+  "type": "string"
+}
  6. Changed1 schema field changed
    • addedOutput schema / properties / symbol / properties / audience
      Added value: +{
+  "type": "string"
+}
  7. Changed3 schema fields changed
    • changedInput schema / properties / fqn / description
      Previous value: -"Fully-qualified core symbol name, with or without the leading backslash. Classes, interfaces, methods and functions all work: Drupal\\Core\\Entity\\EntityInterface, or Drupal\\Core\\Recipe\\RecipeRunner::installModule."New value: +"Core symbol name. Namespaced names with or without the leading backslash (Drupal\\Core\\Entity\\EntityInterface, Drupal\\Core\\Recipe\\RecipeRunner::installModule); a bare function or constant name (check_markup, DRUPAL_DISABLED); or a prefixed pseudo-symbol as what_changed reports it (fn:check_markup, core:hook:preprocess_page, core:library:claro/drupal.shortcut)."
    • addedOutput schema / properties / symbol / properties / removal_in
      Added value: +{
+  "type": "string"
+}
    • removedOutput schema / properties / symbol / properties / removed_in
      Removed value: -{
-  "type": "string"
-}
  8. Changed1 schema field changed
    • addedOutput schema / properties / symbol / properties / placeholder
      Added value: +{
+  "type": "boolean"
+}
  9. First observed

TDQS

A4.9/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 safety is covered. The description adds substantial behavioral detail beyond those annotations: the meaning of status flags like removed, scheduled_removal, deprecated, placeholder; the audience and usage scope; the evidence rollup timestamp; and the exact fallback behavior for unresolved fragments, including ordering and calling again with one fqn.

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 long but dense and well structured: a one-sentence purpose, sibling routing, then terse bullet-like sections for fqn forms, resolved output, and unresolved output. Every sentence carries distinct information; nothing is redundant with the schema or annotations.

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?

For a tool with four parameters, no output schema, and two very different response modes (resolved vs. fragment fallback), the description covers both modes, the field types returned, the sorting and caps, the fqn input forms, and the relevant sibling tools. An agent has enough to invoke the tool correctly and interpret the main output without guessing.

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 schema already documents all four parameters well. The description adds meaningful extra semantics: case-insensitive matching for fragments, public-symbols-only scope, candidates ordering ('entries starting with the fragment come first, then by projects_using'), and the top_projects cap context. This exceeds the baseline of 3.

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 opening sentence states a specific verb and resource: 'Answer is this core symbol safe to use, and who still uses it for one symbol.' It also distinguishes its fragment-lookup behavior from exact symbol lookup and names sibling tools that cover related but different needs, so an agent can tell it apart from list_symbol_users, what_changed, and search_code.

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 explicitly routes to alternatives: 'Every user in pages: list_symbol_users. Changed between versions: what_changed. Code text: search_code.' It also explains when the tool switches from exact lookup to candidate listing ('A name that resolves to nothing returns the catalog entries containing it instead'), giving clear 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
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