VeriApi.Pro

Add or subtract Turkish business days

takvim_is_gunu_ekle

Read-onlyIdempotent

Returns the date N business days after (or before, with a negative value) a start date, skipping weekends, official holidays and religious holidays, plus the skipped days. Use it for delivery, payment and legal deadline dates. The start date itself is not counted.

Endpoint: GET /v1/takvim/is-gunu/ekle. Available on all plans, including free. Costs 1 request unit 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": {
      "gun": "<gun>"
    },
    "name": "takvim_is_gunu_ekle"
  }
}

Input Schema

Name	Required	Description	Default
`gun`	Yes	Number of business days; negative counts backwards.
`arife`	No	Half-day holidays (eves, 28 October): 'is_gunu' (default, counted as working day) or 'tatil'.	is_gunu
`tarih`	No	Start date YYYY-MM-DD; default today.
`cumartesi`	No	true if Saturday is a working day (6-day week). Default false.

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 9, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Goes well beyond the read-only/idempotent annotations: it discloses plan availability (all plans including free), cost (1 request unit per call), the endpoint, and that the response is Turkish JSON with source and guncelleme fields. It also discloses the non-obvious behaviors that skipped days are returned and the start date is not counted.

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?

Front-loaded with the core sentence, then follows with usage and operational facts in a compact block; no filler sentences. The endpoint/plan/cost line is slightly operational clutter but each clause carries information an agent needs.

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

Completeness5/5

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

There is no output schema, yet the description tells the agent what comes back (computed date plus skipped days, Turkish JSON with source and update timestamp). Combined with plan, cost, and edge-case counting rules, nothing needed to call it correctly is missing.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3; the description earns a step up by clarifying the counting semantics ('the start date itself is not counted') and restating the negative-value direction, which changes how 'gun' is interpreted. It does not add anything about the arife or cumartesi parameters beyond the schema.

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?

States a precise verb and resource ('returns the date N business days after or before a start date') and scopes it to Turkish calendar rules — weekends, official holidays, religious holidays. An agent can distinguish it from siblings like takvim_gun and takvim_tatiller without opening either schema.

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 explicit use cases ('delivery, payment and legal deadline dates') and explains the negative-value direction, which is clear guidance. It stops short of naming when to use takvim_gun or takvim_tatiller instead, so the sibling routing is only implied.

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?