Skip to main content
Glama
Michaelzag

Migadu MCP Server

by Michaelzag

get_domain

Read-onlyIdempotent

Retrieve complete configuration and status information for a specified domain in your Migadu account.

Instructions

Get full details for a specific domain.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYes

Implementation Reference

  • The MCP tool handler function for 'get_domain'. Decorated with @migadu_tool, it accepts a domain name and a Context, logs the action, then delegates to the service layer's get_domain method.
    @migadu_tool(mcp, read_only=True)
    async def get_domain(name: str, ctx: Context) -> dict[str, Any]:
        """Get full details for a specific domain."""
        await ctx.info(f"📋 Getting domain {name}")
        return await get_service_factory().domain_service().get_domain(name)
  • The tool has an implicit schema defined by its signature: a required string parameter 'name' and a Context. No separate Pydantic model is used for this read-only tool. The FastMCP framework auto-generates the JSON schema from the type hints.
    async def get_domain(name: str, ctx: Context) -> dict[str, Any]:
        """Get full details for a specific domain."""
        await ctx.info(f"📋 Getting domain {name}")
        return await get_service_factory().domain_service().get_domain(name)
  • The server initialization function calls register_domain_tools(mcp) which registers all domain tools including 'get_domain' on the FastMCP server instance.
    def initialize_server() -> None:
        register_domain_tools(mcp)
  • Inside the @migadu_tool decorator, the function wrapper is registered with FastMCP via mcp.tool(annotations=annotations)(wrapper) with readOnlyHint=True.
        mcp.tool(annotations=annotations)(wrapper)
        return wrapper
    
    return decorator
  • The service layer implementation of get_domain. Makes a GET request to the Migadu API endpoint /domains/{name} to retrieve full domain details.
    async def get_domain(self, name: str) -> dict[str, Any]:
        return await self.client.get(f"/domains/{name}")
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true, and openWorldHint=true. The description adds little beyond stating that it returns 'full details', which is consistent but not particularly insightful.

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?

The description is a single sentence, front-loaded, and contains no unnecessary words. It efficiently conveys the core purpose.

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?

While the description is minimal, it covers the basic intent for a simple get operation. However, lacking output schema and sibling differentiation, it feels incomplete; e.g., what constitutes 'full details' is ambiguous.

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?

The single parameter 'name' is not explained beyond its title. With 0% schema description coverage, the description should provide context (e.g., format, constraints) but does not.

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 description clearly states the verb 'Get', the resource 'domain', and the scope 'full details for a specific domain'. This distinguishes it from sibling tools like list_domains or get_domain_diagnostics.

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?

No guidance is provided on when to use this tool versus alternatives such as get_domain_diagnostics or get_domain_usage. There is no mention of exclusions or prerequisites.

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/Michaelzag/migadu-mcp'

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