Skip to main content
Glama
ElonJask

ProxyPin MCP Server

by ElonJask

get_domains

Retrieve captured domain names with request frequency from ProxyPin's network traffic history for analysis and API structure review.

Instructions

Get list of all captured domains with request counts.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The `get_domains` function is the handler that retrieves and aggregates captured domains and their associated request methods and counts. It is registered as an MCP tool using the `@mcp.tool()` decorator.
    @mcp.tool()
    def get_domains() -> str:
        """Get list of all captured domains with request counts."""
        requests = reader.get_requests(limit=500, detail_level=DetailLevel.SUMMARY)
    
        domains: dict[str, dict[str, Any]] = {}
        for req in requests:
            if not isinstance(req, RequestSummary) or not req.host:
                continue
            entry = domains.setdefault(req.host, {"count": 0, "methods": set()})
            entry["count"] += 1
            entry["methods"].add(req.method)
    
        result = [
            {
                "domain": domain,
                "count": info["count"],
                "methods": sorted(info["methods"]),
            }
            for domain, info in sorted(domains.items(), key=lambda item: -item[1]["count"])
        ]
        return _json_response(result)
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the tool retrieves a list with request counts, implying a read-only operation, but lacks details on permissions, rate limits, data freshness, or error handling. This is insufficient for a tool with no annotation coverage.

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, efficient sentence that directly states the tool's purpose without any wasted words. It is front-loaded and appropriately sized for a simple tool, making it highly concise and well-structured.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool has 0 parameters, an output schema exists, and no annotations, the description is minimally adequate. It explains what the tool does but lacks behavioral context and usage guidelines. With the output schema handling return values, the description meets basic needs but has clear gaps in transparency and guidelines.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has 0 parameters with 100% coverage, so no parameter documentation is needed. The description appropriately doesn't discuss parameters, and since there are none, it doesn't need to compensate for any gaps, meriting a high score.

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 clearly states the verb ('Get') and resource ('list of all captured domains with request counts'), making the purpose specific and understandable. However, it doesn't explicitly differentiate from sibling tools like 'list_requests' or 'search_requests', which might also involve domain-related data, preventing a perfect score.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites, context for 'captured domains', or how it differs from sibling tools such as 'list_requests' or 'search_requests', leaving the agent with minimal usage direction.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/ElonJask/proxypin-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server