Skip to main content
Glama
trthaber-mcp

trthaber-mcp

trthaber_latest

Retrieve breaking news from TRT Haber, ordered by publish time, with an optional 1–30 item limit; returns titles, article URLs, summaries, and publish times.

Instructions

Breaking news (son dakika) from TRT Haber, newest first. limit 1..30 (the page lists ~120 articles). Returns articles (title, article URL, summary when present, publish time when shown).

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

Input Schema

NameRequiredDescriptionDefault
limitNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the burden and does disclose useful behavior: it returns articles rather than a single item, the page holds roughly 120 articles, and results are ordered newest first. It omits whether the operation is read-only (implied), whether only the newest 30 are reachable, and any rate or auth considerations.

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?

Front-loaded with purpose and ordering, then return shape and parameter bounds in two short sentences plus a parenthetical. No filler, though the hard line wrapping and the return-field list (duplicated by the output schema) are slightly wasteful.

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 one-parameter read tool with an output schema and no annotations, this covers purpose, ordering, limit bounds, and the size of the underlying pool. The main residual gap is whether results beyond the top 30 are reachable at all, which matters for an agent planning to page through breaking news.

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?

The single parameter has no schema description, yet the description supplies its valid range (1..30) and the reason for the cap ('the page lists ~120 articles'), which is genuine meaning an agent cannot get from the schema's bare integer type and default of 10.

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?

Names a specific resource and source ('Breaking news (son dakika) from TRT Haber') plus an explicit ordering ('newest first'), which lets an agent distinguish it from search/get_article siblings. It does not differentiate itself from trthaber_headlines, which sounds like the nearest neighbor.

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 by the word 'Breaking' — an agent can infer it is for the current news feed, but there is no explicit statement of when to prefer it over trthaber_headlines or trthaber_search_news, and no prerequisites or exclusions are given.

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