AgentDomain

by MarsHeer

Overview Schema Source Related Servers Discussions Admin

Python

Remote

login

Authenticate with your AgentDomain account credentials to retrieve and store your API key for domain management tasks.

Instructions

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": {
      "email": "<email>",
      "password": "<password>"
    },
    "name": "login"
  }
}

Input Schema

Name	Required	Description	Default
`email`	Yes
`password`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.1.2May 25, 2026

TDQS

C2.9/5.0

Behavior2/5

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

With no annotations, the description must inform about side effects. It mentions 'save the API key' but does not clarify where it is saved, whether credentials are stored, or if it creates a session. No information about error handling or security implications.

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, concise sentence that immediately conveys the core purpose with no extraneous information.

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

Completeness2/5

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

Despite the existence of an output schema, the description omits critical details such as the required nature of inputs, authentication implications, and expected outcomes. For a credential-based login, more context is needed.

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

Parameters1/5

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

Schema description coverage is 0%, and the description provides no additional meaning for the 'email' and 'password' parameters. No format, constraints, or purpose beyond the schema field names are given.

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 action ('Login'), the target resource ('existing AgentDomain account'), and the outcome ('save the API key'). It effectively distinguishes from the sibling tool 'register' by specifying 'existing' account.

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?

The description implies use for existing accounts but provides no explicit guidance on when to use this tool versus alternatives (e.g., 'register' for new accounts). No when-not-to-use or prerequisite conditions are mentioned.

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

Deploy Server