Skip to main content
Glama

Contact and operator details

get_contact
Read-onlyIdempotent

Returns 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

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
emailYesThe email address for starting an engagement.
signalYesA link that opens a Signal chat with the operator.
linkedinYesThe URL of the operator's LinkedIn profile.
locationYesThe city and country where the business is based.
operatorYesWho runs turva.dev and the registered business behind it.
engagementYesHow an engagement is communicated, async_only for written exchange with no calls.
business_idYesThe Finnish business ID of the business.
first_replyYesHow soon the first reply comes and by which channels, and that LinkedIn has no set reply time.
channel_noteYesWhich channel suits which kind of message, and that there are no calls.
how_to_startYesThe steps to start an engagement and the access an audit needs, one per entry.
correspondence_languagesYesISO 639-1 codes of the languages the correspondence is held in.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedOutput schema / properties / operator / properties / legal_page
      Added value: +{
      +  "description": "The turva.dev page that states the terms, the privacy notice and how data is handled.",
      +  "type": "string"
      +}
    • changedOutput schema / properties / operator / required
      Previous value: -[
      -  "name",
      -  "run_by",
      -  "legal_form",
      -  "business_id",
      -  "vat_id",
      -  "location",
      -  "postal_address",
      -  "team",
      -  "background",
      -  "company_page"
      -]New value: +[
      +  "name",
      +  "run_by",
      +  "legal_form",
      +  "business_id",
      +  "vat_id",
      +  "location",
      +  "postal_address",
      +  "team",
      +  "background",
      +  "company_page",
      +  "legal_page"
      +]
  2. Changed2 schema fields changed
    • addedOutput schema / properties / operator / properties / postal_address
      Added value: +{
      +  "description": "The postal address of the business.",
      +  "type": "string"
      +}
    • changedOutput schema / properties / operator / required
      Previous value: -[
      -  "name",
      -  "run_by",
      -  "legal_form",
      -  "business_id",
      -  "vat_id",
      -  "location",
      -  "team",
      -  "background",
      -  "company_page"
      -]New value: +[
      +  "name",
      +  "run_by",
      +  "legal_form",
      +  "business_id",
      +  "vat_id",
      +  "location",
      +  "postal_address",
      +  "team",
      +  "background",
      +  "company_page"
      +]
  3. Changed21 schema fields changed
    • addedOutput schema / properties / business_id / description
      Added value: +"The Finnish business ID of the business."
    • addedOutput schema / properties / channel_note / description
      Added value: +"Which channel suits which kind of message, and that there are no calls."
    • addedOutput schema / properties / correspondence_languages / description
      Added value: +"ISO 639-1 codes of the languages the correspondence is held in."
    • addedOutput schema / properties / correspondence_languages / items / description
      Added value: +"An ISO 639-1 language code."
    • addedOutput schema / properties / email / description
      Added value: +"The email address for starting an engagement."
    • addedOutput schema / properties / engagement / description
      Added value: +"How an engagement is communicated, async_only for written exchange with no calls."
    • addedOutput schema / properties / first_reply / description
      Added value: +"How soon the first reply comes and by which channels, and that LinkedIn has no set reply time."
    • addedOutput schema / properties / how_to_start / description
      Added value: +"The steps to start an engagement and the access an audit needs, one per entry."
    • addedOutput schema / properties / how_to_start / items / description
      Added value: +"One step as a sentence."
    • addedOutput schema / properties / linkedin / description
      Added value: +"The URL of the operator's LinkedIn profile."
    • addedOutput schema / properties / location / description
      Added value: +"The city and country where the business is based."
    • addedOutput schema / properties / operator / description
      Added value: +"Who runs turva.dev and the registered business behind it."
    • addedOutput schema / properties / operator / properties / background / description
      Added value: +"The professional background of the person who runs the business."
    • addedOutput schema / properties / operator / properties / business_id / description
      Added value: +"The Finnish business ID of the business."
    • addedOutput schema / properties / operator / properties / legal_form / description
      Added value: +"The legal form of the business."
    • addedOutput schema / properties / operator / properties / location / description
      Added value: +"Where the business is based: city, region and country."
    • addedOutput schema / properties / operator / properties / name / description
      Added value: +"The trading name of the business."
    • addedOutput schema / properties / operator / properties / run_by / description
      Added value: +"The person who runs the business."
    • addedOutput schema / properties / operator / properties / team / description
      Added value: +"Who works at the business and how clients work with them."
    • addedOutput schema / properties / operator / properties / vat_id / description
      Added value: +"The VAT identification number of the business."
    • addedOutput schema / properties / signal / description
      Added value: +"A link that opens a Signal chat with the operator."
  4. Changed2 schema fields changed
    • addedOutput schema / properties / operator
      Added value: +{
      +  "additionalProperties": false,
      +  "properties": {
      +    "background": {
      +      "type": "string"
      +    },
      +    "business_id": {
      +      "type": "string"
      +    },
      +    "company_page": {
      +      "description": "The turva.dev page that states the business details.",
      +      "type": "string"
      +    },
      +    "legal_form": {
      +      "type": "string"
      +    },
      +    "location": {
      +      "type": "string"
      +    },
      +    "name": {
      +      "type": "string"
      +    },
      +    "run_by": {
      +      "type": "string"
      +    },
      +    "team": {
      +      "type": "string"
      +    },
      +    "vat_id": {
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "name",
      +    "run_by",
      +    "legal_form",
      +    "business_id",
      +    "vat_id",
      +    "location",
      +    "team",
      +    "background",
      +    "company_page"
      +  ],
      +  "type": "object"
      +}
    • changedOutput schema / required
      Previous value: -[
      -  "email",
      -  "signal",
      -  "linkedin",
      -  "business_id",
      -  "location",
      -  "engagement",
      -  "correspondence_languages",
      -  "first_reply",
      -  "channel_note",
      -  "how_to_start"
      -]New value: +[
      +  "email",
      +  "signal",
      +  "linkedin",
      +  "business_id",
      +  "location",
      +  "engagement",
      +  "correspondence_languages",
      +  "first_reply",
      +  "channel_note",
      +  "how_to_start",
      +  "operator"
      +]
  5. Changed3 schema fields changed
    • addedInput schema / $schema
      Added value: +"https://json-schema.org/draft/2020-12/schema"
    • addedInput schema / additionalProperties
      Added value: +false
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "$schema": "https://json-schema.org/draft/2020-12/schema",
      +  "additionalProperties": false,
      +  "properties": {
      +    "business_id": {
      +      "type": "string"
      +    },
      +    "channel_note": {
      +      "type": "string"
      +    },
      +    "correspondence_languages": {
      +      "items": {
      +        "type": "string"
      +      },
      +      "type": "array"
      +    },
      +    "email": {
      +      "type": "string"
      +    },
      +    "engagement": {
      +      "type": "string"
      +    },
      +    "first_reply": {
      +      "type": "string"
      +    },
      +    "how_to_start": {
      +      "items": {
      +        "type": "string"
      +      },
      +      "type": "array"
      +    },
      +    "linkedin": {
      +      "type": "string"
      +    },
      +    "location": {
      +      "type": "string"
      +    },
      +    "signal": {
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "email",
      +    "signal",
      +    "linkedin",
      +    "business_id",
      +    "location",
      +    "engagement",
      +    "correspondence_languages",
      +    "first_reply",
      +    "channel_note",
      +    "how_to_start"
      +  ],
      +  "type": "object"
      +}
  6. Added

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile needs little restating. The description still adds value beyond that by explaining the data is static JSON compiled into the Worker, changes nothing, and only refreshes on deploy, which tells an agent the data can be stale relative to a deploy cycle. What it does not cover is return shape or error behavior, but the output schema exists for that.

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?

Purpose and trigger conditions are front-loaded in the first and fourth sentences, so the agent gets the essentials immediately. The remaining enumeration of returned fields is long and partly duplicates the output schema, which is mild redundancy rather than confusion; every clause is at least grounded in real content, so no sentence is pure filler.

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?

For a static, zero-argument read tool with full annotations and an output schema, the description covers the necessary surface: what it returns, when to call it, what to call instead for commercial data, and how fresh the data is. The only gap is minor duplication of output-schema content, not a missing piece an agent would need.

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?

The tool takes zero parameters and the schema accepts no additional properties, so there is nothing for the description to disambiguate. Baseline for a 0-param tool applies, and the description correctly avoids inventing inputs.

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: returns who runs turva.dev and the official contact channels. It then enumerates the concrete contents (legal form, Business ID, VAT ID, address, email, Signal, LinkedIn, correspondence languages, first-reply time) and explicitly contrasts itself with get_services for product and pricing questions, so an agent can distinguish it from siblings without opening a schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It names concrete triggering questions: who is behind turva.dev, legal or imprint details, how to contact, how to start an audit, what access must be granted. It also states an explicit exclusion and the alternative to use instead (get_services for what is sold and what it costs), so routing is unambiguous in both directions.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources