Skip to main content
Glama

istasyon_bul

Search Istanbul rail station names or spelling variants to retrieve station group, code, line, and date details.

Instructions

İstasyon adını veya yazım varyantını arayarak grup, kod, hat ve tarihleri bulun.

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": {
      "ad": "<ad>"
    },
    "name": "istasyon_bul"
  }
}

Input Schema

NameRequiredDescriptionDefault
adYes
en_fazlaNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It does disclose one meaningful behavioral trait — matching tolerates spelling variants — and enumerates the returned fields, but says nothing about permission requirements, match strictness, ordering, or how ambiguous results are resolved. With an output schema present, the return-value gap is partly covered elsewhere.

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?

A single front-loaded sentence with no filler; every element (input, matching behavior, returned fields) earns its place. It is perhaps too terse for the gaps it leaves, but the structure itself is efficient.

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

Completeness3/5

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

The tool is simple — two flat parameters and an output schema that already documents return values. Still, one parameter is undocumented and there is no routing guidance against two sibling tools, which for a no-annotation tool leaves meaningful gaps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate. It covers the required 'ad' parameter conceptually (station name or spelling variant), but the second parameter 'en_fazla' (max results, default 10) is never mentioned, so the agent gets no meaning for it beyond the bare schema title.

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: search by station name or spelling variant to retrieve group, code, line and dates. An agent can tell what it does and roughly what comes back. It stops short of distinguishing itself from the sibling tools sema and sorgu.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No explicit when-to-use or when-not-to-use guidance, and no alternative tools are named. The mention of 'yazım varyantı' (spelling variant) implies tolerant matching, which hints at appropriate usage, but the agent is left to infer when this tool should be chosen over sema or sorgu.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools