Skip to main content
Glama

Learn AI with Yaakov Tzedek

About the AI TV app

about_ai_tv
Read-onlyIdempotent

What AI TV is (Yaakov Tzedek's AI learning app): platforms, what a subscription includes, current plans and prices as shown on the site, lesson language, and the download and site links.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "about_ai_tv"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNoContent language: "en" English (default) or "he" Hebrew.en

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?

Annotations already cover safety (readOnly, idempotent, non-destructive, closed-world), so the bar is lower; the description still adds valuable context by stating that plans and prices are 'as shown on the site,' signalling a static site snapshot rather than live billing data. With no output schema, the content inventory also implicitly tells the agent what the response will contain.

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?

One compact sentence with a parenthetical identifier followed by a scoped content list; nothing is padded. The fragment style and long enumeration are slightly dense but each item maps to distinct returned content.

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?

For a trivial read-only, zero-required-parameter lookup with no output schema, the description covers what information comes back and where the data originates. It could say more about response shape or currency of pricing, but nothing essential to invoking it correctly 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 single 'lang' enum parameter is fully documented in the schema with a default, so the baseline is 3. The description's mention of 'lesson language' describes a content topic rather than the response-language parameter, which could momentarily be confused with 'lang' but does not add meaning to the parameter itself.

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 names a specific resource ('Yaakov Tzedek's AI learning app') and enumerates the exact content it exposes: platforms, subscription inclusions, plans/prices, lesson language, and download/site links. An agent can tell it apart from siblings like latest_ai_news or get_course, though it never explicitly contrasts itself with them.

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: the content list suggests it fits general 'what is this app / how much does it cost' questions, but there is no explicit when-to-use or when-not-to-use statement, and no sibling is named as an alternative for overlapping questions (e.g. pricing vs. course lookup).

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.