Contact and operator details
get_contactReturns who runs turva.dev and the official ways to reach it. The operator details give the legal form, Business ID, VAT ID and postal address. The rest gives the email address, the Signal link, the LinkedIn profile, the correspondence languages, the first-reply time, the access an audit needs, and links to the company page and to the legal page that states the terms, the privacy notice and how data is handled. Use this when a user asks who is behind turva.dev, for its legal or imprint details, how to contact it, how to start an audit or what access has to be granted. For what is sold and what it costs use get_services instead. Read-only: returns static JSON that is compiled into the Worker, so it changes nothing and updates only on deploy.
Tool call template
This tool declares no required parameters. Add optional parameters from the input schema as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {},
"name": "get_contact"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| Yes | The email address for starting an engagement. | ||
| signal | Yes | A link that opens a Signal chat with the operator. | |
| Yes | The URL of the operator's LinkedIn profile. | ||
| location | Yes | The city and country where the business is based. | |
| operator | Yes | Who runs turva.dev and the registered business behind it. | |
| engagement | Yes | How an engagement is communicated, async_only for written exchange with no calls. | |
| business_id | Yes | The Finnish business ID of the business. | |
| first_reply | Yes | How soon the first reply comes and by which channels, and that LinkedIn has no set reply time. | |
| channel_note | Yes | Which channel suits which kind of message, and that there are no calls. | |
| how_to_start | Yes | The steps to start an engagement and the access an audit needs, one per entry. | |
| correspondence_languages | Yes | ISO 639-1 codes of the languages the correspondence is held in. |