Skip to main content
Glama

Autopedya

Sıfır araç fiyatı

fiyat_ara
Read-only

Türkiye'de satılan sıfır otomobillerin güncel fiyatlarını getirir. Yalnız marka verilirse markanın modellerini başlangıç fiyatlarıyla, marka ve model verilirse modelin tüm versiyonlarını fiyat, yakıt, vites ve kampanya bilgisiyle döndürür.

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": {
      "marka": "<marka>"
    },
    "name": "fiyat_ara"
  }
}

Input Schema

NameRequiredDescriptionDefault
markaYesMarka adı, ör. "Renault", "Mercedes-Benz", "Togg"
modelNoModel adı (isteğe bağlı), ör. "Clio", "T10X"

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint=true, openWorldHint=false), so the description's contribution is the return contract: different payloads per parameter combination plus the fields returned (fiyat, yakıt, vites, kampanya). It does not say how fresh "güncel" prices are or what happens when a brand or model is unknown.

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 and immediately followed by the two invocation modes. No filler, no repetition of the title.

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

Completeness5/5

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

There is no output schema, and the description compensates by enumerating what the response contains in each branch. For a two-parameter read-only lookup, an agent has everything needed to call it correctly.

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 coverage is 100%, so a baseline of 3 applies, but the description earns more by explaining that adding the optional model parameter changes the result shape entirely (model list vs. version-level detail). That is genuine meaning beyond the schema's "Model adı (isteğe bağlı)".

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?

States a specific verb and resource ("Türkiye'de satılan sıfır otomobillerin güncel fiyatlarını getirir") and even describes two distinct operating modes. It never names a sibling such as akaryakit_fiyati or arac_bul, so the boundary with fuel-price or listing tools is left implicit rather than stated.

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?

Gives clear conditional guidance: brand alone yields models with starting prices, brand plus model yields all versions with detail. What it does not do is say when to prefer this tool over the sibling price/listing tools, or note any exclusions.

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