Skip to main content
Glama
Sign In
dolphin-anty-mcp

dolphin-anty-mcp

by someorgyouwontcareabout
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Attach or detach profiles from folders

move_profiles_to_folder

Move browser profiles to a specified folder, or detach them from all folders by omitting folderId.

Instructions

Attach profiles to a folder, or detach them from whatever folder they are in. Omit folderId to detach.

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": {
      "profileIds": "<profileIds>"
    },
    "name": "move_profiles_to_folder"
  }
}

Input Schema

NameRequiredDescriptionDefault
folderIdNoTarget folder. Leave unset to detach the profiles instead.
passwordNoApplied to attached profiles that are password-protected.
profileIdsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

The description adds behavioral context beyond the annotations: it reveals the dual attach/detach behavior and that detaching removes from the current folder. It does not contradict annotations (readOnlyHint=false, destructiveHint=false).

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?

Single concise sentence that front-loads the core action ('Attach profiles to a folder') and then adds the detach exception. No wasted words.

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?

For a 3-parameter tool with no output schema, the description and schema together cover the main operation, attach/detach logic, and the optional password. Missing details like error behavior or what happens if folderId is invalid but overall adequate.

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?

Schema description coverage is 67% (folderId and password have descriptions). The description adds 'Omit folderId to detach,' but this is already in the schema. profileIds lacks description, but its meaning is self-evident from the name.

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 tool attaches profiles to a folder or detaches them, with a specific verb+resource. It distinguishes from sibling folder tools by focusing on the move/attach/detach action.

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 explicit usage guidance: 'Omit folderId to detach' clarifies when to use the detach behavior. However, it does not name alternative tools or provide exclusion criteria beyond attach/detach.

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