Skip to main content
Glama
trthaber-mcp

trthaber-mcp

trthaber_headlines

Retrieve current headlines for a chosen TRT Haber category, returning titles, article URLs, summaries, and publish times. Set category and limit to focus the listing.

Instructions

Top headlines in one TRT Haber category. category: "gundem" (default), "turkiye", "dunya", "turk-dunyasi", "ekonomi", "spor", "savunma", "cocuk", "dunya-disi", "kultur-sanat", "yasam", "saglik", "bilim-teknoloji", "egitim", "cevre", "guncel", "trt-arsiv", "interaktif". limit 1..30 (category pages list 15). Returns headlines (title, article URL, summary when the listing carries one, 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_headlines"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
categoryNogundem

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It does disclose the ordering concept (top headlines), the page size (category pages list 15), the limit bounds, and roughly what the response contains. It says nothing about rate limits, failure behavior, or whether results are cached/stable, which is a meaningful gap for an unannotated tool.

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 lead sentence front-loads the purpose, then parameters are documented compactly. The long category list is verbose but each token is load-bearing since the schema has no enum, so it earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool is simple (two optional params) and an output schema exists, so the return-value sentence is optional extra. What is missing is guidance on how this differs from the search and latest siblings, which an agent needs in order to pick correctly among the five related tools.

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

Parameters5/5

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

Schema coverage is 0% and the schema declares no enums, yet the description supplies the complete accepted category vocabulary including the default 'gundem' and spells out the limit range 1..30 with the default page size of 15. This is exactly the meaning the schema cannot convey and it fully compensates for the gap.

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 states a specific action and resource: fetching top headlines within a single TRT Haber category. The category enumeration makes the scope concrete. It does not explicitly distinguish itself from siblings like trthaber_latest or trthaber_search_news, so an agent must infer the difference from wording alone.

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 'top headlines in one category' and the listed categories, but there is no explicit when-to-use or when-not-to-use instruction and no named alternative. An agent can guess this is the browse-by-category tool rather than search or latest, but must guess.

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