Skip to main content
Glama
Mogacode-ma

infomaniak-mcp-agent

by Mogacode-ma
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

infomaniak_dns_create_record

Destructive

Create a DNS record on an Infomaniak zone with a two-phase commit: first call returns a plan and token, second call applies the change.

Instructions

Create a DNS record on an Infomaniak-managed zone. Two-phase commit: first call returns a plan + token, second call (same params + token) actually creates the record.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
zoneYesDNS zone (root domain) to add the record to, e.g. 'broz.be'. Must be a domain whose DNS is managed by Infomaniak (check via infomaniak_get_domain).
sourceYesSubdomain part (e.g. 'www', 'mail') or '.' for the zone apex. Do NOT include the zone itself.
typeYesRecord type as enum: A, AAAA, CNAME, MX, TXT, NS, SRV, CAA, PTR. Must be UPPERCASE.
targetYesRecord value. For MX and SRV, embed the priority inline as Infomaniak does, e.g. '5 mta-gw.infomaniak.ch'.
ttlNoTime-to-live in seconds. Min 60, max 86400 (24h). Default 3600 (1h).
confirmation_tokenNoToken from the prior plan response. Required on the apply phase only.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.1.2
    • addedInput schema / properties / confirmation_token / description
      Added value: +"Token from the prior plan response. Required on the apply phase only."
    • addedInput schema / properties / ttl / description
      Added value: +"Time-to-live in seconds. Min 60, max 86400 (24h). Default 3600 (1h)."
    • addedInput schema / properties / type / description
      Added value: +"Record type as enum: A, AAAA, CNAME, MX, TXT, NS, SRV, CAA, PTR. Must be UPPERCASE."
    • addedInput schema / properties / zone / description
      Added value: +"DNS zone (root domain) to add the record to, e.g. 'broz.be'. Must be a domain whose DNS is managed by Infomaniak (check via infomaniak_get_domain)."
  2. First observedv0.1.0

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true and readOnlyHint=false; the description adds the critical two-phase commit behavior, explaining that the first call plans and the second with token actually creates. This is valuable beyond structured fields.

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 sentences, first states purpose, second explains the phased behavior. Zero redundancy.

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?

For a non-idempotent, mutating tool with a two-phase protocol, the description captures the essential workflow. The zone prerequisite is mentioned in the description and reinforced in schema; output format is covered by output schema.

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?

Schema covers 100% of parameters with rich descriptions. Description adds the cross-phase constraint that all params must be identical except the token, which clarifies how confirmation_token interacts with other parameters.

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 uses specific verb 'Create' with resource 'DNS record' and scope 'Infomaniak-managed zone'. The two-phase commit detail distinguishes this create tool from update/delete/list siblings.

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?

Provides clear context: use to create a DNS record on a managed zone, and outlines the two-phase procedure. Does not name sibling alternatives explicitly, but the verb and resource make the intended use unambiguous.

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