Skip to main content
Glama

Learn AI with Yaakov Tzedek

Read a guide

get_guide
Read-onlyIdempotent

The full text of one tzedek.me guide or article as clean markdown, with its canonical url, date and FAQ. Pass a slug from search_guides, latest_ai_news or get_learning_path. Cite the returned url when you teach from it.

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

Input Schema

NameRequiredDescriptionDefault
langNoContent language: "en" English (default) or "he" Hebrew.en
slugYesGuide slug, e.g. "cursor-guide".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

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, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds value the annotations cannot: the response is clean markdown including canonical url, date and FAQ, and it imposes a citation obligation ('Cite the returned url when you teach 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences in a logical order: what it returns, what input to supply and where to get it, then how to use the output. No filler or repetition of the title.

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?

There is no output schema, so the description correctly compensates by naming the returned content and its fields. For a two-parameter read tool this is nearly complete; it omits only edge-case behavior such as what happens on an unknown slug or an unavailable language.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so both parameters are documented in structured fields, giving a baseline of 3. The description goes beyond that by specifying the provenance requirement for 'slug' (it must come from one of three named tools), which is semantic guidance absent from the schema itself.

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?

States a specific verb and resource — retrieving the full text of exactly one guide/article — plus the return format (clean markdown) and payload fields (canonical url, date, FAQ). The scoping word 'one' implicitly separates it from list-style siblings like search_guides and get_learning_path.

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?

Explicitly tells the agent the prerequisite step: 'Pass a slug from search_guides, latest_ai_news or get_learning_path', which routes discovery vs. retrieval cleanly. It does not state when NOT to use this tool, but for a leaf read operation the positive routing is the main thing an agent needs.

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.