Skip to main content
Glama

Learn AI with Yaakov Tzedek

Search AI guides

search_guides
Read-onlyIdempotent

Search Yaakov Tzedek's practical AI guides and articles on tzedek.me (Claude, Claude Code, ChatGPT, AI agents, MCP, automation, AI video and images, AI for business). Returns title, summary, date and the canonical url of each match. Use get_guide with a returned slug to read the full guide. lang "en" searches the English guides, "he" the larger Hebrew library.

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_guides"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNoContent language: "en" English (default) or "he" Hebrew.en
limitNo
queryYesWhat to learn about, e.g. "Claude Code skills" or "build an AI agent".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive behavior, so the safety profile is covered. The description adds genuine value by naming the returned fields (title, summary, date, canonical url) and the language scope. It does not mention result limits, ranking, or empty-result behavior, so it stays moderate.

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?

Three tight sentences ordered as purpose, return shape, next step, then language note. The parenthetical topic list is keyword-dense but does help an agent match user phrasing. Minor waste only.

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 carries the return-shape burden and does so. A single read-only search with three params is well covered; the only missing piece an agent might need is what limit does and whether results are ranked.

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 67%, and the description reinforces lang semantics ("en" English guides, "he" the larger Hebrew library), which is useful beyond the enum. However, the limit parameter (default 5, max 20) has no description in the schema and is never mentioned or explained in the description, leaving a real gap.

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 a well-scoped resource (Yaakov Tzedek's practical AI guides and articles on tzedek.me), plus a topic list that tells the agent what corpus is covered. It also names the sibling get_guide and its role, so the agent can separate search from read 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 get_guide with a returned slug to read the full guide" gives an explicit follow-up path, and the lang sentence tells the agent which corpus to pick and that Hebrew is larger. It lacks an explicit when-not or a statement of what to do if zero matches return, so it falls short of full alternative routing.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.