Glushkov Modelling MCP

List tutorial taxonomy

list_tutorial_taxonomy

Read-only. Returns tutorial categories, tags, and difficulty levels currently used by educational articles, together with the number of tutorials assigned to each value. Tags include ACF metadata: facet (component | technique | material | context), status (active | deprecated), and publicFilter (whether the tag is shown in UI filters). Use includeDeprecated=true to include deprecated tags for audit purposes (excluded by default). Use groupByFacet=true to receive tags grouped by their facet type instead of a flat list. Use this tool before calling get_tutorials with tag, category, or level filters when the exact available value is unknown. Use get_tutorials to retrieve tutorials matching selected taxonomy values. This tool returns taxonomy metadata, not tutorial articles. Values are ordered by tutorial count in descending order. If no tutorials are available, returns empty categories, tags, and levels arrays.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`groupByFacet`	No	When true, returns tags grouped by facet type (component, technique, material, context, unclassified) instead of a flat sorted list.
`includeDeprecated`	No	When true, includes tags with status='deprecated' in the result. Default: false (only active tags are returned).

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedSep 24, 2026

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"
+}

First observedSep 9, 2026

TDQS

A4.4/5.0

Behavior4/5

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

No annotations are provided, so the description carries the full burden. It discloses read-only behavior, default exclusions (deprecated tags excluded by default), ordering (by tutorial count descending), and empty-result behavior. It also explains the meaning of tag metadata (facet, status, publicFilter). This is strong behavioral disclosure, though it doesn't mention pagination or rate limits, which are less relevant for a taxonomy list.

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 detailed but every sentence earns its place: it covers scope, metadata semantics, parameter behavior, usage context, and edge cases. It is front-loaded with the read-only nature and core return value. Slightly long, but not bloated given the complexity of the taxonomy metadata.

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 read-only list tool with two optional boolean parameters and no output schema, the description is complete. It explains what is returned, how values are ordered, what the tag metadata means, how parameters affect output, and what happens when no tutorials exist. An agent has everything needed to call it correctly.

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

Parameters3/5

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

Schema description coverage is 100%, so the schema already documents both parameters. The description adds context by explaining the purpose of includeDeprecated ('for audit purposes') and groupByFacet ('grouped by their facet type'), but it doesn't add significant new meaning beyond the schema. Baseline 3 is appropriate.

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 verb ('Returns') and resource ('tutorial categories, tags, and difficulty levels'), and explicitly distinguishes itself from get_tutorials ('This tool returns taxonomy metadata, not tutorial articles'). It also names sibling tools and clarifies scope, so an agent can tell it apart from get_tutorials and search_tutorial_content without opening schemas.

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 says when to use this tool: 'Use this tool before calling get_tutorials with tag, category, or level filters when the exact available value is unknown.' It also names the alternative (get_tutorials) and what it does instead. This is clear, actionable routing guidance.

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 tools Inspect

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

Need Help?