Skip to main content
Glama
Sign In

Glushkov Modelling MCP

by com.glushkov-modelling
OverviewDiscussionsAdmin

List tutorial taxonomy

list_tutorial_taxonomy

Read-only. Returns the shared taxonomy dictionary used by both tutorials and gallery photos, plus tutorial categories and difficulty levels with tutorial counts. Tags come from the TutorialTags taxonomy (ACF Tutorial Tag Settings) with status='active' and are listed only when assigned to at least one tutorial or at least one gallery photo. Each tag has slug, name, facet (component | technique | material | context | view | unclassified), status, publicFilter (shown in tutorial UI filters), count (number of tutorials), photoCount (number of gallery photos), and appliesTo — an array with 'tutorials', 'gallery', or both, computed from actual assignments (cached up to 60 minutes). Use tags with 'tutorials' in appliesTo as values for get_tutorials tag/tagFacet filters, and tags with 'gallery' in appliesTo as values for list_gallery_photos tag/tagFacet filters. Use appliesTo='tutorials' or appliesTo='gallery' to return only tags used in that area. Use includeDeprecated=true to also include non-active (deprecated or hidden) tags for audit purposes. Use groupByFacet=true to receive tags grouped by facet instead of a flat list. Tags are ordered by tutorial count, then photo count, descending; categories and levels by tutorial count. This tool returns taxonomy metadata, not tutorial articles or photos. If nothing is available, returns empty categories, tags, and levels arrays.

Input Schema

NameRequiredDescriptionDefault
appliesToNoOptional filter: 'tutorials' returns only tags assigned to at least one tutorial, 'gallery' only tags assigned to at least one gallery photo. When omitted, returns tags used in either area.
groupByFacetNoWhen true, returns tags grouped by facet (component, technique, material, context, view, unclassified) instead of a flat sorted list.
includeDeprecatedNoWhen true, also includes tags whose status is not 'active' (deprecated or hidden), if they are assigned to tutorials or photos. Default: false (only active tags are returned).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / appliesTo
      Added value: +{
+  "description": "Optional filter: 'tutorials' returns only tags assigned to at least one tutorial, 'gallery' only tags assigned to at least one gallery photo. When omitted, returns tags used in either area.",
+  "enum": [
+    "tutorials",
+    "gallery"
+  ],
+  "type": "string"
+}
    • changedInput schema / properties / groupByFacet / description
      Previous value: -"When true, returns tags grouped by facet type (component, technique, material, context, unclassified) instead of a flat sorted list."New value: +"When true, returns tags grouped by facet (component, technique, material, context, view, unclassified) instead of a flat sorted list."
    • changedInput schema / properties / includeDeprecated / description
      Previous value: -"When true, includes tags with status='deprecated' in the result. Default: false (only active tags are returned)."New value: +"When true, also includes tags whose status is not 'active' (deprecated or hidden), if they are assigned to tutorials or photos. Default: false (only active tags are returned)."
  2. Changed3 schema fields changed
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / groupByFacet
      Added value: +{
+  "default": false,
+  "description": "When true, returns tags grouped by facet type (component, technique, material, context, unclassified) instead of a flat sorted list.",
+  "type": "boolean"
+}
    • addedInput schema / properties / includeDeprecated
      Added value: +{
+  "default": false,
+  "description": "When true, includes tags with status='deprecated' in the result. Default: false (only active tags are returned).",
+  "type": "boolean"
+}
  3. First observed

TDQS

A4.8/5.0
Behavior5/5

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

With no annotations, the description carries the full burden and does so: it declares 'Read-only', discloses the 60-minute cache, the active-status default and what includeDeprecated changes, ordering rules, and the empty-arrays fallback. These are behavioral traits the schema does not express.

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?

Front-loaded with the read-only signal and the core return shape, and every sentence carries information an agent needs. It is dense and long, but not padded; a small trim of enumerated field lists would tighten it further.

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 enumerates the returned fields (slug, name, facet, status, publicFilter, count, photoCount, appliesTo) and the facet enum values, plus categories/levels ordering and the empty-result case, so an agent can consume the response 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 baseline is 3; the description nonetheless adds value beyond the schema by framing appliesTo values as filter inputs for other tools and explaining includeDeprecated as an audit use case rather than just a boolean flag.

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?

States a specific verb and resource ('Returns the shared taxonomy dictionary... plus tutorial categories and difficulty levels') and explicitly excludes what it is not ('returns taxonomy metadata, not tutorial articles or photos'), which cleanly separates it from siblings like get_tutorials and list_gallery_photos.

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?

Gives explicit routing: tags with 'tutorials' in appliesTo feed get_tutorials tag/tagFacet filters, tags with 'gallery' feed list_gallery_photos filters, and it names when to use appliesTo, includeDeprecated (audit purposes), and groupByFacet. When-to-use and cross-tool alternatives are both covered.

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

All Glushkov Modelling MCP 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