Skip to main content
Glama

Autopedya

Autopedya'da ara

site_ara
Read-only

Autopedya'da arama yapar: fiyat listeleri, marka sayfaları, haberler, rehber ve ansiklopedi yazıları, akaryakıt ve satış verileri. Başlık, adres ve kısa açıklama 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": {
      "sorgu": "<sorgu>"
    },
    "name": "site_ara"
  }
}

Input Schema

NameRequiredDescriptionDefault
turNoYalnız bu türde ara (isteğe bağlı)
adetNoSonuç sayısı, 1–20 (varsayılan 8)
sorguYesAranacak kelimeler, ör. "elektrikli suv", "mtv hesaplama"

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/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 the return shape (title, address, short description), which is genuinely useful given there is no output schema, but it says nothing about result limits, ranking, or empty-result behavior beyond what the schema's 'adet' parameter implies.

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?

Two tight sentences: the first front-loads what is searched and where, the second states the return fields. No filler, though the content-type list is somewhat long and could be trimmed without loss.

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 read-only search tool with full schema coverage and no output schema, the description supplies the missing piece — the return fields — and scopes the corpus. Only the absence of guidance on narrowing via 'tur' versus using a specialized sibling keeps it from being complete.

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%, with each parameter (sorgu, tur, adet) documented including an enum and a default, so the schema carries the parameter burden. The description adds no meaning beyond it — it does not explain how 'tur' interacts with the listed content categories, which would have been a valuable addition.

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 (arama yapar) and resource (Autopedya) and enumerates the content types covered — price lists, brand pages, news, guides, encyclopedia, fuel and sales data. This makes it recognizable as the broad/general search tool, but it never explicitly contrasts itself with siblings like fiyat_ara or son_haberler, so differentiation is left to inference.

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?

The breadth of content types implies this is the general-purpose search entry point, which is useful context. However, there is no explicit when-to-use/when-not guidance and no named alternative for narrower searches (e.g. price-only or news-only), so the agent must infer routing from sibling names alone.

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