Skip to main content
Glama
henrikogaard

infomaniak-admin-mcp

by henrikogaard

infomaniak_get_domain_full

Read-onlyIdempotent

Retrieve complete Infomaniak domain details including EPP transfer code, transfer and trade status, DNS health diagnostics, registrant info, and associated products—by domain ID or FQDN.

Instructions

Full domain detail including auth_code (EPP transfer code), transfer_status, trade_status, termination state, glue records, TLD/registry info, attached service (web hosting), DNS detail, DNS health diagnostic, owner (registrant), associated products on the domain AND its subdomains, and the DNS logs API URL. Accepts either domain_id or FQDN. Manager-private.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
domainYesEither the numeric domain id (e.g. '1938345') OR the FQDN (e.g. 'agensea.net'). Both work. Discover via infomaniak_list_domains.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYes
dnsNo
tldNo
infoNo
errorNo
ownerNo
usersNo
is_idnNo
rightsNo
statusNo
optionsNo
productNo
serviceNo
synonymNo
has_mailNo
registryNo
synonymsNo
auth_codeNo
has_errorNo
puny_codeNo
has_dnssecNo
is_premiumNo
is_synonymNo
restorableNo
is_externalNo
terminationNo
extra_fieldsNo
glue_recordsNo
trade_statusNo
customer_nameYes
domain_statusNo
authcode_quotaNo
diagnostic_dnsNo
is_city_domainNo
use_custom_urlNo
transfer_statusNo
dns_logs_api_urlNo
is_dnssec_pendingNo
is_part_of_ksuiteNo
has_infomaniak_dnsNo
has_whois_antispamNo
associated_productsNo
has_trustee_contactNo
is_dns_managed_by_infomaniakNo
is_service_mail_domain_aliasNo
subdomain_associated_productsNo
is_service_mail_on_other_accountNo
Behavior4/5

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

Annotations already cover read-only/idempotent safety, so the description adds value by listing the specific data categories returned and the manager-level access requirement. No contradictions with annotations.

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?

Description is a single efficient sentence that front-loads the purpose and uses a concise list of included data. Every item is specific and non-redundant.

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?

With a rich output schema present, the description covers all necessary behavioral context: input formats, included data, and access requirements. It is fully sufficient for selecting and invoking the tool.

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?

The single parameter 'domain' is fully described in the schema (100% coverage); the description only briefly reiterates ID/FQDN acceptance without adding format or discovery details beyond what the schema provides.

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?

Description clearly states it returns 'Full domain detail' and enumerates specific fields (auth_code, transfer_status, DNS health, etc.), distinguishing it from simpler domain tools like infomaniak_get_domain. The verb+resource+scope is specific and unambiguous.

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?

It states the accepted input forms (domain_id or FQDN) and notes 'Manager-private' access, giving clear context for invocation. It does not explicitly name alternative tools or exclusions, but the scope is evident from the detailed field list.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/henrikogaard/infomaniak-admin-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server