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

dolphin-anty-mcp

by someorgyouwontcareabout
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

List proxies

list_proxies
Read-only

Retrieve a paginated list of proxies stored in your workspace. Filter by proxy name or host to quickly locate specific entries.

Instructions

List proxies saved in the workspace, with optional search and pagination.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_proxies"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNo
limitNo
queryNoSearch by proxy name or host.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, so the agent knows it's safe. The description adds workspace scoping and optional search/pagination, but no other behavior details like return format or pagination semantics.

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 sentence, 11 words, front-loaded with the action and resource, no filler.

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 simple list tool with read-only annotation and schema displaying constraints, the description is sufficient to convey purpose and optional parameters, though it doesn't detail return structure.

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 covers only 33% of parameters with descriptions (query). The description mentions search and pagination, providing some context for parameters, but page and limit lack detailed descriptions beyond schema constraints.

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 it lists proxies saved in the workspace, with a specific verb and resource. It distinguishes from sibling list tools for other resources (e.g., list_profiles, list_statuses).

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?

It implies usage for retrieving proxies from the workspace. There are no alternatives for listing proxies among siblings, so context is clear, but it doesn't explicitly state when to use or not use it.

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