VeriApi.Pro

Nearest EV charging stations

sarj_yakin

Read-onlyIdempotent

Returns licensed electric-vehicle charging stations nearest to a coordinate, sorted by distance: operator, address, sockets (AC/DC, type, kW), public or private. Paid plans only.

Endpoint: GET /v1/sarj/yakin. Requires a paid plan (free plan returns 403). Costs 5 request units per call. Read-only; JSON in Turkish with source and guncelleme (updated at) fields.

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": {
      "enlem": "<enlem>",
      "boylam": "<boylam>"
    },
    "name": "sarj_yakin"
  }
}

Input Schema

Name	Required	Description
`dc`	No	true = only stations with DC (fast) sockets; false = only AC.
`enlem`	Yes	Latitude (WGS84).
`limit`	No	Maximum number of stations (default 20).
`soket`	No	Comma-separated socket types, e.g. 'ccs2,type2'.
`boylam`	Yes	Longitude (WGS84).
`min_kw`	No	Minimum highest socket power in kW, e.g. 50.
`yaricap`	No	Search radius in km (default 10, max 100).
`operator`	No	Comma-separated operator codes or ids, e.g. 'zes,esarj,trugo'.
`herkese_acik`	No	true to exclude private (customer / staff only) stations.

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 9, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the description is free to add cost (5 request units per call), failure behavior (403 on free plans), and output characteristics (JSON in Turkish with source and `guncelleme` fields). That is real value beyond the structured fields, though pagination/truncation behavior for `limit` is not discussed.

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?

The first sentence front-loads what the tool returns and how it is sorted, followed by the endpoint, cost and output-format facts. Minor waste: "Paid plans only" is restated as "Requires a paid plan (free plan returns 403)" in the next sentence.

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?

With 9 parameters and no output schema, the description carries the return-value burden and does so (enumerating station fields and the `guncelleme` timestamp), plus the Turkish-language and paid-plan constraints. Only edge-case behavior such as empty results or radius-vs-limit interaction is left unspecified.

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%, so every parameter including `dc`, `soket`, `min_kw`, `operator` and `herkese_acik` is already documented at the schema level. The description adds no syntax or format guidance beyond the schema, so the baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Names a specific verb and resource ("Returns licensed electric-vehicle charging stations nearest to a coordinate"), plus result ordering ("sorted by distance") and the fields returned (operator, address, sockets with AC/DC, type, kW, public/private). No sibling in the list covers EV charging, so there is no ambiguity to resolve.

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 a hard prerequisite ("Paid plans only", free plan returns 403) and a cost per call, which tells the agent when the tool is viable. It does not discuss alternatives or when to prefer a different sibling; that gap is minor since no sibling overlaps functionally.

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

All VeriApi.Pro tools Inspect

Try in Browser

Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?