Skip to main content
Glama
trthaber-mcp

trthaber-mcp

trthaber_get_article

Retrieves the full text and metadata of a TRT Haber article from its trthaber.com URL, including title, spot, publish date, description, image, and body content.

Instructions

Full text of one TRT Haber article. article_url: the article's trthaber.com URL (as returned by the headlines/latest/search tools, e.g. "https://www.trthaber.com/haber/bilim-teknoloji/ guney-torid-goktasi-yagmuru-bu-gece-nadir-gorulen-ates-toplari- olusturacak-962288.html"). Returns title, spot, publish date, description, image and the full body text.

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": {
      "article_url": "<article_url>"
    },
    "name": "trthaber_get_article"
  }
}

Input Schema

NameRequiredDescriptionDefault
article_urlYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A4.1/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full behavioral burden. It does disclose what the call returns (title, spot, publish date, description, image, body text), which is useful, but says nothing about rate limits, auth, error behavior on a malformed or dead URL, or content that may be missing. For a simple read-only fetch this is adequate but not rich.

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 the purpose in the first sentence, then the parameter meaning, then return shape. The single very long example URL consumes a large share of the text but earnestly earns its place by fixing the exact URL shape; otherwise there is no 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?

An output schema exists, so the enumerated return fields are partly redundant, but the description leaves nothing an agent needs in order to invoke the tool correctly. Given a one-parameter read-only fetch, the definition is sufficiently complete.

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?

Schema description coverage is 0%, so the description must compensate and largely does: it defines article_url as the article's trthaber.com URL and supplies a concrete fully-qualified example including the numeric ID suffix, which pins down the expected format far beyond the bare string type in the schema.

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 — full text of ONE article from TRT Haber — and scopes it to a single item, which cleanly distinguishes it from the headline/latest/search siblings that return lists. An agent can tell immediately this is the detail-fetch step of a two-stage flow.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly tells the agent where the input comes from (the headlines/latest/search tools), which implies the correct sequence: list first, then fetch full text. It stops short of stating exclusions or what to do when an article is unavailable, but the usage context is clear.

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