ShowMeStepByStep

by io.github.rt1966

search_tutorials

Search the ShowMeStepByStep tutorial corpus by free-text query. Searches across tutorial titles, descriptions, and step content. Returns slim summaries with TL;DRs and canonical URLs. Tenant-aware. Optional filters narrow by category, difficulty, or maximum duration.

Input Schema

TableJSON Schema

Name	Required	Description
`limit`	No
`query`	Yes	Search query (>= 2 chars)
`difficulty`	No	Optional difficulty filter.
`categorySlug`	No	Optional category to restrict the search to (e.g. 'cooking', 'crochet'). Use list_categories to see available slugs.
`maxDurationMinutes`	No	Optional ceiling on tutorial total duration. Useful for 'quick recipes' / 'under 10 min' queries.

Schema Changelog

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

Changed3 schema fields changedMay 23, 2026

addedInput schema / properties / categorySlug

Added value: +{
+  "description": "Optional category to restrict the search to (e.g. 'cooking', 'crochet'). Use list_categories to see available slugs.",
+  "type": "string"
+}

addedInput schema / properties / difficulty

Added value: +{
+  "description": "Optional difficulty filter.",
+  "enum": [
+    "easy",
+    "intermediate",
+    "advanced"
+  ],
+  "type": "string"
+}

addedInput schema / properties / maxDurationMinutes

Added value: +{
+  "description": "Optional ceiling on tutorial total duration. Useful for 'quick recipes' / 'under 10 min' queries.",
+  "minimum": 1,
+  "type": "integer"
+}

First observedMay 21, 2026

TDQS

A4.4/5.0

Behavior4/5

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

With no annotations provided, the description carries the full burden. It discloses the search scope, return format ('slim summaries with TL;DRs and canonical URLs'), tenant-awareness, and optional filters. It does not mention rate limits or auth, but the read-only nature is strongly implied by 'Search' and the return description is more specific than typical.

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 three sentences: the first establishes the core purpose, the second details search scope and return format, the third introduces filters. Each sentence earns its place, and the key verb+resource is front-loaded. No filler or repetition.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool with 5 parameters, no output schema, and no annotations, the description covers the essential input/output contract: what the query matches, what results look like, and available filters. It lacks explicit details on result ordering/pagination and does not point to get_tutorial for full content, but overall it is sufficient for selecting and invoking the tool correctly.

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?

The input schema covers 80% of parameters (all but limit, which has self-documenting default/min/max). The description adds meaning beyond the schema by clarifying that the query matches titles, descriptions, and step content, and by giving a concrete use case for maxDurationMinutes ('quick recipes' / 'under 10 min'). This enriches the schema without redundancy.

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 an explicit verb and resource: 'Search the ShowMeStepByStep tutorial corpus by free-text query.' It further specifies the search scope ('titles, descriptions, and step content') and distinguishes itself from sibling listing tools (e.g., list_tutorials_by_category, list_recent_tutorials) by focusing on free-text search across content.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides clear context for use: it is for free-text search, returns slim summaries (implying use get_tutorial for full details), and supports optional filters. However, it does not explicitly name alternatives or state when not to use this tool, so it stops short of full exclusionary guidance.

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

All ShowMeStepByStep tools Inspect

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

Disambiguation5/5

Each tool has a clearly distinct purpose: get_tutorial fetches a specific item, list_categories/ list_recent_tutorials/ list_tutorials_by_category handle different listing views, search_tutorials is free-text search, and request_tutorial is the only write operation. No two tools overlap in intent.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern in snake_case: get_ for single resource, list_ for collections, search_ for search, request_ for submission. The naming is uniform and predictable.

Tool Count5/5

Six tools is squarely in the ideal 3-15 range for a content-focused server. Each tool covers a distinct need (discover, browse, fetch, request) and none feel redundant or missing.

Completeness5/5

The domain is a tutorial discovery platform, and the surface covers the full consumer journey: browse by category or recency, search, fetch full details, and request missing content. No critical gaps exist; related tutorials are even provided within get_tutorial.

Resources

Need Help?