Skip to main content
Glama

Bursa arsa ve tarla bilgisi ara

bursaarsa_ara
Read-onlyIdempotent

Bursa'da arsa, tarla, tapu, imar, miras, hisseli tapu, vergi ve dolandırıcılık konularında BursaArsa'nın doğrulanmış kısa cevaplarını ve kaynak sayfalarını getirir. Türkçe soru ya da anahtar kelime verin.

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": {
      "soru": "<soru>"
    },
    "name": "bursaarsa_ara"
  }
}

Input Schema

NameRequiredDescriptionDefault
soruYesTürkçe soru ya da anahtar kelime, ör. 'miras kalan tarla nasıl satılır'

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, idempotentHint, non-destructive and closed-world behavior, so the safety profile is fully covered without description help. The description adds useful behavioral context beyond that: results are 'doğrulanmş kısa cevaplar ve kaynak sayfalar' (verified short answers with source pages), which tells the agent what kind of content comes back. It does not say what happens when no verified answer exists, whether results are paginated, or how current the answers are.

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 sentences, front-loaded with the verb and resource before the topic enumeration. The topic list is long but functional — it defines scope rather than padding. Slight redundancy between the title and description costs it a perfect score.

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 single-parameter, read-only retrieval tool with no output schema, the description supplies the essential missing pieces: the return content type (verified short answers plus source pages), the geographic and topical boundary (Bursa only), and the input language. Only edge-case behavior — empty results, answer recency — is left unaddressed, which is acceptable at this complexity.

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%, and the single parameter already carries its own description plus a concrete example ('miras kalan tarla nasıl satılır'). The description's instruction to provide a Turkish question or keyword largely restates the schema. Baseline 3 applies since the schema does the heavy lifting and nothing new is added.

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 concrete verb ('getirir' — retrieves) plus a specific resource: BursaArsa's verified short answers and source pages. The long topic list (arsa, tarla, tapu, imar, miras, vergi, dolandırıcılık) pins down the domain precisely, so an agent knows what this tool covers. No sibling tools exist, so there is nothing to differentiate against, which keeps it just below a top score.

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 second sentence tells the caller to supply a Turkish question or keyword, which signals the input mode but not when to prefer this tool over other approaches. There are no exclusions, no statement of when not to use it, and no alternatives named (none exist in the sibling list). The language requirement is the only real constraint given.

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