Skip to main content
Glama

Son otomotiv haberleri

son_haberler
Read-only

Autopedya'daki en son otomotiv haberlerini başlık, tarih ve adresle döndürür. İsteğe bağlı bir kelimeyle (ör. marka adı) süzülebilir.

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

Input Schema

NameRequiredDescriptionDefault
adetNoHaber sayısı, 1–20 (varsayılan 10)
konuNoBaşlıkta geçmesi gereken kelime, ör. "Togg", "kampanya" (isteğe bağlı)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered; the description adds real value by disclosing recency ordering ('en son') and the exact fields returned despite there being no output schema. It stays silent on pagination or how results are ordered beyond recency, which keeps it from a 5.

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 short sentences that front-load the resource and return shape before the optional filtering note. No filler, no repetition of the title, every clause carries information.

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 zero-required-parameter read tool with a fully documented two-parameter schema, no output schema and clear annotations, the description supplies everything needed to call it correctly, including the return fields. Only the absence of any note on result ordering/limits beyond 'en son' leaves a small gap.

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 description coverage is 100%, so both 'adet' and 'konu' are already documented with ranges, defaults and examples. The description repeats the optional-keyword concept and adds a brand-name example, but adds no constraint or syntax beyond what the schema provides, so the baseline 3 applies.

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 verb and resource ('en son otomotiv haberlerini ... döndürür') and even enumerates the returned fields (başlık, tarih, adres), so an agent knows exactly what it gets. It does not explicitly contrast itself with the sibling site_ara, which could plausibly cover similar news-lookup intents, so it falls short of a 5.

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 mention of an optional keyword filter (e.g. brand name) hints at the filtered-lookup case, and 'en son' implies a browse-latest case. There is no explicit statement of when to prefer this over site_ara or the other siblings, and no when-not guidance.

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.

Resources