Skip to main content
Glama

Learn AI with Yaakov Tzedek

Latest AI news

latest_ai_news
Read-onlyIdempotent

The latest AI news articles from tzedek.me, newest first, with title, summary, date and url. lang "he" is the daily Hebrew news desk; "en" the English news articles.

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": "latest_ai_news"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

The annotations already declare a safe, idempotent, closed-world read, so the description's main burden is behavioral detail. It usefully adds the source (tzedek.me), the ordering ('newest first') and the shape of each item, but says nothing about how many articles come back, how 'limit' interacts with the max of 20, or how fresh the feed is.

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 the resource, source and ordering, followed by the language distinction. Every clause carries information and nothing is repeated for padding.

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 two-parameter read tool with no output schema, the description covers what comes back, in what order, and from where. The only material omission is the meaning of 'limit' (how many articles are returned per call), which keeps it short of a 5.

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 50%: 'lang' is fully documented in the schema, yet the description adds a useful nuance the enum cannot ('he' is the daily Hebrew news desk). The 'limit' parameter is never explained anywhere, and the description does not compensate for that gap, so it sits at the baseline.

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 ('The latest AI news articles'), the source domain, the ordering ('newest first') and the returned fields ('title, summary, date and url'). None of the sibling tools (about_ai_tv, get_course, get_guide, get_learning_path, list_courses, search_guides) return a news feed, so an agent can distinguish this reliably.

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?

The second sentence gives real selection guidance for the language switch, describing 'he' as the daily Hebrew news desk and 'en' as English news articles, which helps an agent choose a value. However, it never states when to reach for this tool versus the sibling guide/course tools, nor any exclusions or prerequisites.

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.