Temsor API — Turkey & EU business data

Turkish Service-of-Process Clock

tr_tebligat_clock

Computes the deemed-received date and the HMK deadline (with holiday shifting) for a Turkish notification, from the date the underlying event actually happened.

Turkish notification law (7201) ties the deadline clock to an event that is not "the date on the letter" — for electronic notification the UETS platform reports send, read AND reached dates, and only the reached date starts the clock (art. 7/a: deemed received 5 calendar days after reaching the address, whether or not it was opened). HMK adds two more rules on top: the day of notification itself does not count (art. 92 — the period starts the next day) and if the computed last day lands on a weekend or a full public/religious holiday, it moves to the next business day (art. 93); a half-day eve (arife) does not shift it. What this will not tell you: whether the notification was itself valid, or what a specific periodType (itiraz, temyiz, cevap…) is in days for your case — that number differs by statute and we do not guess it; supply periodDays yourself. Only the "hmk" law family is covered so far.

Input Schema

TableJSON Schema

Name	Required	Description
`type`	Yes	Notification method. Determines which event `basisDate` refers to and whether the deemed-received date is same-day or shifted.
`basisDate`	Yes	The date `basisLabel` describes for this type — for "electronic" this is the date UETS reports the message as reached, not sent or read.
`lawFamily`	Yes	Body of procedural law the period is computed under. Only "hmk" (Code of Civil Procedure) is supported so far.
`periodDays`	Yes	Length of the statutory or judicial period, in days, counted from `periodStart`.
`periodType`	No	Free-text label for the period (e.g. "itiraz", "temyiz"), echoed back only — not mapped to a day count.
`hasAttorney`	No	Whether the addressee has a registered attorney of record. When true and `type` is not "vekil", a TK 11 warning is added noting that service should have gone to the attorney.
`ilanenDeemedDays`	No	Only valid with type "ilanen": number of days the competent authority set for the notice to become deemed received (TK 31), 7-15, default 7. Not the number of days for the underlying period.
`subjectToJudicialRecess`	No	Whether this matter is subject to the judicial recess (adli tatil, HMK 104) instead of being exempt. Only affects the result when `lawFamily` is "hmk" and the computed last day falls in the 20 July - 31 August window.

TDQS

A4.7/5.0

Behavior5/5

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

With no annotations provided, the description carries the full burden, and it delivers thoroughly. It explains the legal rules under Turkish notification law (7201) and HMK, including the deemed-received calculation, holiday shifting, and arife exceptions. It also discloses constraints (only 'hmk' supported, no guessing of period days) and the meaning of basisDate for electronic notifications. This goes well beyond what a schema could convey.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Although lengthy, every sentence contributes substantive legal or usage information. The purpose is front-loaded, followed by relevant legal background, then explicit limitations. There is no fluff or redundancy; the density is justified by the tool's complexity.

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?

For a complex legal-computation tool with 8 parameters and no output schema, the description is remarkably complete. It explains the underlying law, the computation logic, edge cases (arife, judicial recess), and what it does not do. An agent has all necessary context to decide whether and how to call the tool, and to interpret its result.

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%, and each parameter already has a descriptive definition (e.g., 'type' explains the meaning of basisDate). The description adds valuable legal context—such as why basisDate for electronic is the reached date, and the significance of hasAttorney—which enriches understating beyond the schema. This is more than the baseline 3, but the schema already does a lot of work.

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 description opens with a precise, verb-led statement: 'Computes the deemed-received date and the HMK deadline (with holiday shifting) for a Turkish notification, from the date the underlying event actually happened.' This clearly identifies the resource (Turkish notification deadlines) and the exact computation performed, distinguishing it from all sibling validation/lookup tools.

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?

The description explicitly states what it does NOT cover: 'What this will not tell you: whether the notification was itself valid, or what a specific periodType... is in days for your case' and advises the caller to supply periodDays themselves. It also notes the limitation to the 'hmk' law family. However, it does not explicitly compare against alternative tools since none of the siblings are similar, so it falls just short of a 5.

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

All Temsor API — Turkey & EU business data tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4/5.0

Disambiguation4/5

Most tools have clearly distinct purposes (e.g., bic_validate vs vin_validate), but there is notable overlap: tr_validate bundles Turkish validations that are also covered individually by iban_validate and tin_validate. Also, lei_validate and lei_lookup are closely related but distinct enough. Overall, agents can usually pick the right tool, but a few pairs could confuse.

Naming Consistency4/5

Tool names are consistently snake_case with predominately verb_noun patterns (e.g., validate, lookup, screen, parse, build). Some nouns like mcp_index, model_archive, and series_history break the verb pattern but are still predictable. Minor deviations from the noun_verb form (tr_invoice_build, shipping_identify) don't cause confusion. Very readable and consistent overall.

Tool Count3/5

With 27 tools, the set is heavy, exceeding the typical 3–15 well-scoped range. However, the server covers a broad domain: international standards validation, Turkey-specific business data (fuel, labor, invoices, addresses), and even MCP/LLM model archives. The count is justifiable given the scope, but it stretches coherence and may overwhelm agents.

Completeness4/5

The tool surface is remarkably comprehensive for the stated Turkey & EU business data purpose: validators for most ID types, VAT, IBAN, phone, VIN, sanctions; plus Turkey-specific operations like invoice build/parse, labor calculations, fuel prices, business days, and address parsing. Minor gaps exist (e.g., no general exchange-rate conversion, no credit-note-specific builder), but agents can accomplish core workflows without dead ends.

Resources

Need Help?