Skip to main content
Glama
Sign In
kualat-mcp

kualat-mcp

by kualatLinks
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

List domains

list_domains
Read-only

Retrieve branded domains linked to your kua.lat account and check their DNS status to verify correct domain configuration.

Instructions

Branded domains connected to the account and their DNS status.

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": "list_domains"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNo
limitNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description adds that results are scoped to the account and include DNS status, which is useful content-level context. It says nothing about pagination behavior, ordering, or what happens with large domain sets, so it does not go far beyond the annotations.

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

Conciseness3/5

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

It is a single efficient fragment with no wasted words, but the brevity is closer to under-specification than to disciplined concision. Adding one short clause on pagination would cost little and close the main gap.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple, no-required-parameter read tool with no output schema, the description is enough to identify what comes back (domains plus DNS status). It is not enough for an agent to know how to iterate results or handle a large account, which is the remaining hole.

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

Parameters2/5

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

There are two parameters (page, limit) with 0% schema description coverage, and the description does not mention pagination, page size, or defaults at all. With the schema silent and the description silent, the agent learns nothing about how to page through domains.

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?

The description names a specific resource ('Branded domains connected to the account') and the payload ('their DNS status'), which goes beyond the bare title 'List domains'. It is a noun phrase with no verb, but the listing operation is unambiguous and no sibling (links, webhooks, account) overlaps.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no prerequisites, and no mention of alternatives such as get_account for account-level data. The agent must infer that this is the correct tool whenever domain information is needed.

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

Deploy Server

Other Tools