Remove a saved domain
remove_saved_domainDestructive
Drop one name from the caller's shortlist.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| domain | Yes | The saved name to remove. |
Onymu
by com.onymu
Schema Changelog
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
- First observed
TDQS
A3.6/5.0
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already provide the safety profile (destructiveHint=true, readOnlyHint=false, idempotentHint=false), and the description is consistent with them, adding the caller-scope and one-item detail. It does not describe irreversibility, error behavior, or what happens if the domain is not currently saved, but the annotation coverage lowers the burden.
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?
A single seven-word sentence that states the action and scope with zero filler. The key meaning is front-loaded and easy to scan.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness4/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The tool is low-complexity with one required parameter, no output schema, and annotations that carry the destructive and read-only hints. The description is sufficient for an agent to invoke it correctly, though it could mention not-found behavior or confirmation semantics.
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 input schema has 100% description coverage: the only parameter, domain, is documented as 'The saved name to remove,' which matches the tool description's wording. The description adds no extra meaning, format, or example beyond what the schema already provides, so the baseline of 3 applies.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose4/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description 'Drop one name from the caller's shortlist' uses an active verb (drop) and clearly names the resource (a saved domain/name), so an agent knows this removes one saved domain. It does not explicitly differentiate from the related sibling remove_favorite_tld, so it misses the top score.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines3/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
The phrase 'from the caller's shortlist' implies this is the right tool when the user wants to remove a previously saved domain, which gives implied context for use. However, it offers no when-not-to-use guidance or alternative routing (e.g., pointing to remove_favorite_tld for TLD removal).
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Try in Browser
Glama MCP Gateway
Add one secure layer between your agents and this server.
TDQS
A4.2/5.0
Disambiguation5/5
Each tool targets a distinct resource or action: domain availability search, username checking, candidate generation, saved domains, favorite TLDs, and recent history are clearly separated. There is no meaningful overlap that would cause an agent to select the wrong tool.
Naming Consistency4/5
Tool names follow a mostly consistent verb_noun snake_case pattern, but there are minor variations: favorites use add/remove/list, saved domains use save/remove/list, and history uses get_recent_* rather than list_*. These are predictable per resource but not perfectly uniform across the set.
Tool Count5/5
Eleven tools is well-scoped for the domain of brand name availability. Each tool earns its place and maps to a clear step in the workflow: searching domains, checking usernames, generating candidates, saving names, managing favorite TLDs, and reviewing recent activity.
Completeness5/5
The tool surface covers the full lifecycle of the domain: searching availability, checking social handles, generating candidates, saving/removing/listings saved names, managing favorite extensions, and reading recent history. There are no obvious dead ends or missing operations that would block the primary workflows.