Skip to main content
Glama

Autopedya

Bütçeye göre araç bul

arac_bul
Read-only

Bütçeye ve isteğe göre Türkiye'de satılan en uygun fiyatlı sıfır otomobilleri bulur. Her model için koşullara uyan en ucuz versiyonu fiyata göre sıralı 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": {
      "butce_max": "<butce_max>"
    },
    "name": "arac_bul"
  }
}

Input Schema

NameRequiredDescriptionDefault
adetNoSonuç sayısı, 1–30 (varsayılan 10)
kasaNoKasa tipi (isteğe bağlı)
yakitNoYakıt türü (isteğe bağlı). hibrit tam ve hafif hibriti, phev şarj edilebilir hibriti kapsar.
otomatikNotrue ise yalnız otomatik vitesli versiyonlar (isteğe bağlı)
butce_maxYesEn yüksek fiyat, TL (ör. 2000000)
butce_minNoEn düşük fiyat, TL (isteğe bağlı)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds real behavioral value by disclosing the result shape (cheapest conforming variant per model, price-sorted), but says nothing about the result-count cap, empty-result behavior, or whether the catalogue is a fixed snapshot.

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 tight sentences with zero filler. The core behavior is front-loaded in the first sentence and the return semantics follow immediately.

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?

There is no output schema, and the description compensates by explaining that results are price-sorted and deduplicated to one cheapest variant per model, which is the key thing an agent needs to interpret the response. Minor gaps remain around result limits and empty-result handling, but the definition is sufficient for correct invocation.

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 coverage is 100%, with descriptions and enums for budget bounds, body type, fuel type, transmission and result count, so the schema carries the parameter burden. The description adds only the vague 'koşullara uyan' phrasing and no detail on how budget bounds or filters combine, so 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?

States a specific verb and resource: finds the most affordable new (zero-km) cars sold in Turkey, sorted by price, one cheapest variant per model. That is far more precise than the title alone and clearly not a fuel-price or news tool. It stops short of naming a sibling to contrast with, so it lands at 4 rather than 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 budget-driven framing ('bütçeye ve isteğe göre') suggests this is the tool for 'what new car can I get for X TL'. There is no explicit when-to-use, no when-not, and no alternative named among fiyat_ara or the other siblings.

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