Skip to main content
Glama

Glushkov Modelling MCP

by com.glushkov-modelling
OverviewDiscussionsAdmin

Get tutorials

get_tutorials

Read-only. Returns educational tutorials from the site, optionally filtered by tag, category, tagFacet, or difficulty level. Use this tool to browse tutorials and filter them by taxonomy. When a slug is provided, it returns the content and metadata for one tutorial. Use get_tutorial_by_title when the user knows an article title but not its slug. Use search_tutorial_content when the user knows only a term, technique, material, tool, or instruction that may occur inside a tutorial. Use list_tutorial_taxonomy when the exact available category, tag, or difficulty-level value is unknown. Without a slug, returns tutorial summaries and metadata. Each tag object includes name, slug, and facet (component | technique | material | context | null). If no tutorials match the filters, returns an empty tutorials array. If a provided slug does not exist, returns a not-found result.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tagNoOptional filter for tutorial tags. Preferred format: slug (lowercase, hyphen-separated), e.g. 'standing-rigging', 'wood-bending', 'double-planking'. Display names are also accepted (e.g. 'Standing Rigging'). Matching is case-insensitive and partial — 'rigging' matches both 'standing-rigging' and 'running-rigging'. Applies only when slug is omitted.
slugNoOptional stable tutorial slug. When provided, returns the complete content and metadata for one tutorial. When omitted, returns a filtered list of tutorial summaries.
levelNoOptional filter for tutorial difficulty level. Uses an exact match, for example 'beginner'. Applies only when slug is omitted.
categoryNoOptional filter for tutorial categories. Uses a case-insensitive partial match against category names. Applies only when slug is omitted.
tagFacetNoOptional filter for tutorial tags by facet type. component — structural parts of the model (Hull, Deck, Masts…); technique — build methods (Caulking, Wood Bending, Blackening…); material — materials used (Wood, Brass, Thread…); context — themes or use-case labels (Standing Rigging, Running Rigging…). Can be combined with the tag filter. Applies only when slug is omitted.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / tag / description
      Previous value: -"Optional filter for tutorial tags. Uses a case-insensitive partial match against tag names. Applies only when slug is omitted."New value: +"Optional filter for tutorial tags. Preferred format: slug (lowercase, hyphen-separated), e.g. 'standing-rigging', 'wood-bending', 'double-planking'. Display names are also accepted (e.g. 'Standing Rigging'). Matching is case-insensitive and partial — 'rigging' matches both 'standing-rigging' and 'running-rigging'. Applies only when slug is omitted."
    • addedInput schema / properties / tagFacet
      Added value: +{
+  "description": "Optional filter for tutorial tags by facet type. component — structural parts of the model (Hull, Deck, Masts…); technique — build methods (Caulking, Wood Bending, Blackening…); material — materials used (Wood, Brass, Thread…); context — themes or use-case labels (Standing Rigging, Running Rigging…). Can be combined with the tag filter. Applies only when slug is omitted.",
+  "enum": [
+    "component",
+    "technique",
+    "material",
+    "context"
+  ],
+  "type": "string"
+}
  2. Changed4 schema fields changed
    • changedInput schema / properties / category / description
      Previous value: -"Filter the list of articles by category (partial match of the category name)."New value: +"Optional filter for tutorial categories. Uses a case-insensitive partial match against category names. Applies only when slug is omitted."
    • changedInput schema / properties / level / description
      Previous value: -"Article list filter by difficulty level (exact match, e.g., 'beginner')."New value: +"Optional filter for tutorial difficulty level. Uses an exact match, for example 'beginner'. Applies only when slug is omitted."
    • changedInput schema / properties / slug / description
      Previous value: -"The slug of a specific educational article. If not specified, a list of all articles is returned."New value: +"Optional stable tutorial slug. When provided, returns the complete content and metadata for one tutorial. When omitted, returns a filtered list of tutorial summaries."
    • changedInput schema / properties / tag / description
      Previous value: -"Article list filter by tag (partial tag name match, case-insensitive)."New value: +"Optional filter for tutorial tags. Uses a case-insensitive partial match against tag names. Applies only when slug is omitted."
  3. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Since no annotations are provided, the description carries the full burden. It discloses that the tool is read-only, returns summaries without a slug, returns full content with a slug, includes behavior for no matches (empty array) and non-existent slugs (not-found result). This is substantial behavioral context, though it could go further (e.g., pagination, rate limits).

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 comprehensive yet structured: it starts with a clear statement of purpose, lists filters, explains parameter interactions, and provides routing guidance. Every sentence adds value, and the key behavioral distinction (with/without slug) is front-loaded. Despite its length, it is efficient for a tool with 5 parameters and multiple sibling alternatives.

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?

Given the tool's complexity (5 optional parameters, multiple filtering modes, sibling alternatives) and lack of annotations and output schema, the description covers all essential aspects: what it returns, filter behavior, edge cases (empty results, not-found), and routing to alternatives. It is complete for an agent to invoke correctly without needing additional documentation.

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%, and the schema already provides detailed descriptions for each parameter, including format hints like 'slug (lowercase, hyphen-separated)' and match behavior. The description does not add much beyond what the schema provides, so a baseline of 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 clearly states the tool's purpose: 'Returns educational tutorials from the site' and explains filtering options. It distinguishes itself from siblings by naming specific alternatives and their use cases, such as get_tutorial_by_title and search_tutorial_content. This provides clear differentiation.

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 versus alternatives: 'Use get_tutorial_by_title when the user knows an article title but not its slug. Use search_tutorial_content when the user knows only a term... Use list_tutorial_taxonomy when the exact available category, tag, or difficulty-level value is unknown.' This is excellent 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 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