VeriApiPro

Write an amount in Turkish words

cevir_yaziyla

Read-onlyIdempotent

Converts a number or money amount to Turkish words following official spelling: plain text, upper case, joined form and the invoice form 'YALNIZ: … TÜRK LİRASI … KURUŞ'. Kuruş is rounded to 2 digits. Without a currency it also returns the ordinal form.

Endpoint: GET /v1/cevir/yaziyla. 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": {
      "tutar": "<tutar>"
    },
    "name": "cevir_yaziyla"
  }
}

Input Schema

Name	Required	Description	Default
`para`	No	Currency: TRY (default), USD, EUR, GBP, CHF; empty string for a plain number.	TRY
`tutar`	Yes	Amount; '1250,50', '1250.50' and '1.250,50' are all accepted.

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, non-destructive behavior, so the bar is lower, yet the description adds real context: GET endpoint, availability on the free plan, 1-request-unit cost, kuruş rounding to 2 digits, and conditional ordinal output. It stops short of describing the response envelope fully, so it is strong rather than exhaustive.

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 output formats are front-loaded and the sentence packs several concrete facts without padding. The trailing endpoint/plan/cost sentence is operational rather than essential to invoking the tool but is short and defensible.

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 no output schema, the description compensates by naming the return format (JSON in Turkish) and key fields (`source`, `guncelleme`) plus the invoice-form string shape. Together with full schema coverage, an agent has enough to call it correctly, though the exact response structure remains only sketched.

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 a 3 would be defensible, but the description adds meaning the schema does not: the absence of a currency (empty string / no `para`) changes the output to include the ordinal form, and kuruş handling is fixed at 2-digit rounding. That clarifies parameter effects rather than restating them.

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?

The first sentence gives a specific verb and resource ('Converts a number or money amount to Turkish words') and enumerates the exact output forms produced. This clearly separates it from the sibling cevir_doviz, which converts currencies rather than rendering amounts as words.

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 implied rather than stated: the description notes that omitting a currency yields the ordinal form and that the tool costs 1 request unit on all plans, which helps decide whether to call it. However, it never explicitly says when to prefer this over cevir_doviz or other conversion siblings, and offers no exclusions.

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

All VeriApiPro tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?