Execute any adm.tools API endpoint directly by specifying an action path and JSON parameters. Use for advanced operations not covered by standard tools.
Call any adm.tools API endpoint directly (advanced)
| Name | Required | Description | Default |
|---|---|---|---|
| action | Yes | API action path (e.g. dns/list, billing/balance_get, domain/check) | |
| params | No | JSON object of POST parameters |
Changes observed during successful MCP inspections.
v2.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
There are no annotations and no output schema, so the description carries the full behavioral burden. It does not mention authentication, response format, error behavior, rate limits, or whether raw endpoints can perform destructive mutations. It only restates the operation.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, front-loaded sentence with no redundancy. 'Advanced' adds a compact signal about intended use, though the overall terseness limits the behavioral and selection guidance it can provide.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given no annotations, no output schema, and a set of sibling tools that should usually be preferred for domain/DNS/mail operations, the description leaves tool selection and behavioral expectations to inference. The parameter schema covers invocation, but the tool's role and safety profile are incomplete.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, and both parameters include useful descriptions and examples. The description adds no parameter-level information, but the schema fully documents the inputs, so the baseline of 3 applies.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description states a clear action ('Call') on a clear resource ('any adm.tools API endpoint') and the word 'directly' signals this is the raw, generic access path. It distinguishes itself from the sibling wrappers by scope, though it does not explicitly name an alternative.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
There is no guidance about when to use this raw endpoint versus sibling tools like adm_domains, adm_dns_records, or adm_balance. 'Advanced' implies it is not for routine use, but no exclusions, preferences, or alternative routing are given.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.