Skip to main content
Glama
Vaartix MCP server

Vaartix MCP server

Official
by vaartix-mail

Get domain

get_domain
Read-only

Retrieve a sending domain by ID to confirm whether it is verified and list the DNS records it needs.

Instructions

Get one sending domain: whether it is verified, and the DNS records it needs. Needs read access: a full-access API key, or the read permission when signed in.

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": {
      "id": "<id>"
    },
    "name": "get_domain"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesVaartix domain ID, e.g. dom_5bvatg1v837anztd

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.3.2

TDQS

A3.8/5.0
Behavior4/5

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

The annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered; the description goes beyond them by disclosing the authorization model (full-access API key or the read permission when signed in), which is genuine behavioral context an agent needs before calling. It also previews the payload content (verification state plus required DNS records), though it does not cover error behavior for unknown IDs.

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?

Two compact sentences: the first states the operation and its return content, the second states access requirements. Nothing is redundant and the key information is front-loaded.

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 one-parameter read with no output schema, the description covers purpose, return content, and auth prerequisites, which is enough to invoke it correctly. Only failure behavior for an invalid or unknown domain ID is left unstated, a minor gap.

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

Parameters3/5

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

There is a single required parameter and the schema already documents it at 100% coverage with a regex pattern and example ID. The description adds no further meaning about the ID format or lookup behavior beyond what the schema supplies, so the baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Get one sending domain" names a specific verb and resource, and the clause "whether it is verified, and the DNS records it needs" tells the agent exactly what the single-object read returns. The word "one" implicitly contrasts with the list_domains sibling, though no sibling is named explicitly.

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?

The description makes clear this is a single-domain lookup rather than a listing, and states the access prerequisites, which is useful context. It does not explicitly say when to prefer this over list_domains or what to do when the domain is not found, so guidance is implied rather than spelled out.

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