Skip to main content
Glama
Sign In
aparser-mcp

aparser-mcp

by izzipizzy
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript

Get proxies

get_proxies

Retrieve live proxies from proxy checkers as IP:port pairs with associated types. Optionally filter results by specific checker names.

Instructions

Get live proxies from the proxy checkers as {"ip:port": ["type", ...]}.

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": "get_proxies"
  }
}

Input Schema

NameRequiredDescriptionDefault
checkersNoOptional list of checker names to filter by. Omit for all.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.3

TDQS

A3.8/5.0
Behavior3/5

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

No annotations are provided, so the description carries full burden. It explains the output format but does not disclose whether the operation is read-only, resource consumption, or any side effects. The description is adequate but lacks explicit behavioral clarity.

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 sentence that conveys the essential information without any superfluous content. It is optimally concise.

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?

Given the tool's simplicity (one optional parameter, no output schema, no annotations), the description is largely complete. It covers the purpose, resource, and output format. However, it could mention potential error conditions or limits for completeness.

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% coverage with a clear description for the 'checkers' parameter. The description does not add semantic value beyond what the schema provides, so baseline score of 3 applies.

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 verb 'Get' and the resource 'live proxies from the proxy checkers', and specifies the output format. It distinguishes from sibling tools which focus on tasks, parsers, or system info.

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 description implies usage for retrieving proxy data but does not explicitly state when to use this tool vs alternatives, nor provides context for when not to 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