Skip to main content
Glama
Sign In

The Daily Workflow — AI Tools & Free Alternatives

by com.thedailyworkflow
OverviewDiscussionsAdmin

get_tutorial_details

Read-onlyIdempotent

Full tutorial content (markdown) with all steps, code blocks, screenshots.

Args:
    slug: Tutorial slug (from search_mcp_tutorials).
    lang: en | ru. Default: en.

Returns:
    Dict with title, summary, content (full markdown), difficulty, category,
    target_client, target_server, target_category, estimated_minutes,
    word_count, views_count, page_url.

Use this AFTER finding a relevant tutorial via search. The `content` field has
full markdown — render it directly to the user, or extract the install commands
/ config snippets they asked about.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "slug": "<slug>"
    },
    "name": "get_tutorial_details"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNoOutput language: "en" for English or "ru" for Russian. Default: "en".en
slugYesTutorial slug - take it from the `slug` field of search_mcp_tutorials results.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, openWorld), so the bar is lower. The description adds genuinely useful behavior: the exact return fields, that `content` is full markdown to render directly, and that install commands or config snippets can be extracted from it.

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 with the payload description, then a compact Args/Returns block and a closing usage note. The Args block duplicates the schema and could be trimmed, but nothing is padded or ambiguous.

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?

This is a simple two-parameter read tool with no output schema, and the description compensates by enumerating the return fields and explaining how to use the markdown content. Nothing an agent needs to call or use the result 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 coverage is 100% and the description's Args section largely restates the schema ('slug from search_mcp_tutorials', 'lang: en | ru, default en'). It adds little meaning beyond the structured fields, 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?

The first line states a specific verb and resource: fetches full tutorial content as markdown including steps, code blocks and screenshots. It also names the sibling that produces the input ('slug from search_mcp_tutorials'), so an agent can distinguish this detail-fetch from the search tools without opening a schema.

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?

'Use this AFTER finding a relevant tutorial via search' gives explicit sequencing relative to search_mcp_tutorials. There are no when-not conditions or statements about what to do if the slug is unknown, but the ordering guidance is 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 toolsInspect
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.

Resources