Skip to main content
Glama

ShowMeStepByStep

by io.github.rt1966
OverviewDiscussionsAdmin

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
NameRequiredDescriptionDefault
limitNo
queryYesSearch query (>= 2 chars)
difficultyNoOptional difficulty filter.
categorySlugNoOptional category to restrict the search to (e.g. 'cooking', 'crochet'). Use list_categories to see available slugs.
maxDurationMinutesNoOptional ceiling on tutorial total duration. Useful for 'quick recipes' / 'under 10 min' queries.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / difficulty / enum
      Previous value: -[
-  "easy",
-  "intermediate",
-  "advanced"
-]New value: +[
+  "easy",
+  "medium",
+  "advanced"
+]
  2. Changed3 schema fields changed
    • 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"
+}
  3. First observed

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries full burden; it usefully discloses the return shape (slim summaries with TL;DRs and canonical URLs) and that the tool is tenant-aware. However, it omits pagination/ranking behavior, result limits, and empty-result handling for a tool with a limit parameter.

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?

Four compact sentences, front-loaded with the core action and scope. Each sentence carries information; minor redundancy between the free-text search statement and the filter sentence, but no filler.

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?

No output schema exists, so the description appropriately summarizes return values (slim summaries, TL;DRs, URLs) and flags tenant-awareness. With 80% schema coverage and only one required parameter, an agent has enough to invoke it correctly; only ranking/pagination semantics are missing.

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 coverage is 80%, so the schema already documents query, difficulty, categorySlug, and maxDurationMinutes. The description only restates 'filters narrow by category, difficulty, or maximum duration,' adding no syntax or format detail beyond the schema. Baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb ('Search') and resource ('ShowMeStepByStep tutorial corpus') plus the fields searched (titles, descriptions, step content). The verb 'search' clearly distinguishes it from the get_/list_ siblings, though it does not name them explicitly.

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

Usage Guidelines3/5

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

The description implies use for free-text lookups and notes that filters narrow results, but never says when to prefer it over list_tutorials_by_category, list_recent_tutorials, or list_categories. No exclusions or explicit trigger conditions are given.

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

All ShowMeStepByStep 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