Skip to main content
Glama

Learn AI with Yaakov Tzedek

Course syllabus

get_course
Read-onlyIdempotent

One course from tzedek.me: description, the syllabus (lesson titles in order), lesson count, total minutes when known, which lessons are free to preview, the price as shown on the site and the course url. Lesson videos and paid lesson content are never returned; the learner watches them on tzedek.me or in the AI TV app.

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

Input Schema

NameRequiredDescriptionDefault
langNoContent language: "en" English (default) or "he" Hebrew.en
slugYesCourse slug from list_courses, e.g. "claude-code-video-course".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

The annotations already establish read-only, idempotent, non-destructive behavior, so the description does not need to repeat safety traits. It adds useful scope information by stating what is returned and explicitly noting that lesson videos and paid lesson content are never returned, which helps set expectations.

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?

The description is compact and front-loads the resource and returned fields. The one long enumeration is dense but purposeful, and the second sentence adds a meaningful exclusion rather than filler.

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 appropriately lists the important return fields and states what is excluded. This is enough for an agent to call and interpret the tool, though it could mention basic error behavior for invalid slugs.

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 both slug and lang are fully documented in the input schema, including enum and example. The description adds no parameter-specific meaning beyond what the schema already provides, so the baseline of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly identifies the resource as one course from tzedek.me and enumerates the returned fields, so the core purpose is unambiguous. It does not explicitly distinguish itself from list_courses or other siblings, which keeps it from a 5.

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 implied by 'One course' and the schema note that slug comes from list_courses, but the description itself gives no explicit when-to-use guidance, alternatives, or exclusions. The agent can infer this is the detail lookup after listing courses, but it is not stated.

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.