The Daily Workflow — AI Tools & Free Alternatives

search_mcp_tutorials

Read-onlyIdempotent

Search 147+ MCP tutorials covering install, configuration, comparison, build guides.

Tutorials are curated step-by-step guides for installing and using MCP servers
with specific clients (Claude Desktop, Cursor, Cline, Windsurf), best-of-category
roundups, build-your-own-server walkthroughs, and concept explainers.

Args:
    query: Free-text search over titles, summaries, keywords. Example: "cursor mcp",
           "build python mcp server", "windsurf vs cursor".
    category: Filter by category. Values: client_setup, category_best, build, usecase,
              install, comparison, concept, general.
    difficulty: Filter by level. Values: beginner, intermediate, advanced.
    lang: Output language (en|ru). Default: en.
    limit: Max results (1-25, default 10).

Returns:
    Dict with `count` and `results`. Each result: slug, title, summary,
    difficulty, category, tutorial_type, estimated_minutes, related_servers,
    page_url.

Use this when the user asks "how do I install X MCP", "best MCPs for Cursor",
"how to build my own MCP server", or hits an MCP setup problem. Follow up with
get_tutorial_details(slug) for the full markdown.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "search_mcp_tutorials"
  }
}

Input Schema

Name	Required	Description	Default
`lang`	No	Output language: "en" for English or "ru" for Russian. Default: "en".	en
`limit`	No	Maximum number of results to return (1-25; values outside the range are clamped). Default: 10.
`query`	No	Free-text search query matched against tutorial titles, summaries and keywords. Example: "cursor mcp", "build python mcp server", "windsurf vs cursor". Empty string returns unfiltered results.
`category`	No	Filter by tutorial category. One of: "client_setup", "category_best", "build", "usecase", "install", "comparison", "concept", "general". Empty string means any category.
`difficulty`	No	Filter by tutorial difficulty. One of: "beginner", "intermediate", "advanced". Empty string means any difficulty.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 3, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and openWorld, so the safety profile is covered. The description adds what annotations cannot: the return envelope (`count` and `results`) with per-result fields, plus the two-step detail-retrieval workflow. It does not mention ranking/relevance behavior or empty-result handling, which keeps it from a 5.

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 purpose and usage trigger, with clearly labeled Args/Returns sections. The Returns block earns its place because there is no output schema, but the Args block duplicates already-complete schema text, which is noticeable waste in an otherwise disciplined description.

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, zero-required-parameter search, the description supplies corpus scope, filter vocabularies, query examples, return fields and the follow-up tool. Nothing an agent needs to call it correctly or to chain into detail retrieval is 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 description coverage is 100%, so the schema already documents every parameter including enums, defaults and the 1-25 clamp. The description's Args block largely restates that, adding only illustrative query strings ('windsurf vs cursor'), so the baseline 3 applies.

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?

A specific verb-plus-resource ('Search 147+ MCP tutorials') with the corpus scope and content types spelled out (client setup, best-of roundups, build walkthroughs, concept explainers). This clearly separates it from sibling searches like search_mcp_servers, search_ai_tools and search_prompts without needing to open any schema.

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?

Names concrete user phrasings that should trigger it ('how do I install X MCP', 'best MCPs for Cursor', 'how to build my own MCP server', setup problems) and explicitly routes the follow-up step to get_tutorial_details(slug). The only gap is no explicit 'do not use for X' against search_qa_cases, but the trigger list plus next-step tool makes selection unambiguous.

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

All The Daily Workflow — AI Tools & Free Alternatives tools Inspect

Try in Browser

Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.