KIRUPA Tutorials & Code Library

Search kirupa.com Tutorials & Articles

search_tutorials

Read-onlyIdempotent

Search hundreds of tutorials and articles on kirupa.com covering JavaScript, TypeScript, CSS, HTML5 Canvas, animations, React, and data structures & algorithms using full-text search (FTS5 + BM25). Returns matching tutorials with canonical URLs, clean Markdown URLs, matching section headings, and excerpts.

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": {
      "query": "<query>"
    },
    "name": "search_tutorials"
  }
}

Input Schema

Name	Required	Description
`limit`	No	Maximum number of tutorials to return (1 to 15, default 5).
`query`	Yes	Keywords, concept, or technical question to search for (e.g. "requestAnimationFrame delta time", "quicksort", "canvas starfield", "closures").
`section`	No	Optional section filter: data_structures_algorithms, javascript, html5, canvas, animations, react, codingexercises, ai, product_development, podcast, or hodgepodge.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 19, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds value beyond that by naming the ranking engine (FTS5 + BM25) and enumerating what comes back (canonical URLs, Markdown URLs, matching section headings, excerpts), though it omits result ordering and pagination behavior.

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?

Two sentences, front-loaded with what is searched and the corpus scope, then what is returned. Every clause carries information (topics, engine, return fields) with no filler or repetition of the name.

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?

With no output schema, the description correctly compensates by enumerating the return fields, and annotations cover the safety profile. It is slightly short of complete because it does not describe ranking order or how the limit interacts with the section filter, but nothing critical to a correct call 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% and all three parameters (query, limit, section) are documented in the schema with defaults, bounds, and examples. The description adds no parameter-level detail such as query syntax rules or how the section filter interacts with ranking, 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?

Names a specific verb (search) and resource (hundreds of tutorials and articles on kirupa.com), states topical scope (JavaScript, TypeScript, CSS, HTML5 Canvas, animations, React, DSA), and discloses the retrieval mechanism (FTS5 + BM25). The search-vs-fetch distinction from get_tutorial is implicit in the verb, so an agent can place it 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 Guidelines3/5

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

Usage is only implied by the verb and topic list; there is no explicit when-to-use, when-not-to-use, or routing to siblings like get_tutorial or find_related_links. An agent can infer this is the entry-point discovery tool, but nothing is stated outright.

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

All KIRUPA Tutorials & Code Library tools Inspect

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

Need Help?