Skip to main content
Glama
ElonJask

ProxyPin MCP Server

by ElonJask

get_request

Retrieve detailed HTTP request data including headers and body content from ProxyPin's network capture history for analysis and API structure examination.

Instructions

Get detailed information for a single request.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
request_idYes
include_bodyNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The 'get_request' tool handler, which retrieves detailed request information using the reader.
    @mcp.tool()
    def get_request(
        request_id: str,
        include_body: bool = True,
    ) -> str:
        """Get detailed information for a single request."""
        if not request_id.strip():
            return _json_response({"error": "request_id is required"})
    
        detail_level = DetailLevel.FULL if include_body else DetailLevel.KEY
        request = reader.get_request_by_id(request_id, detail_level)
        if request is None:
            return _json_response({"error": f"Request {request_id} not found"})
    
        result = request.model_dump()
        if isinstance(request, RequestFull):
            result["curl_command"] = request.to_curl()
        return _json_response(result)
    
    
    @mcp.tool()
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states this is a read operation ('Get'), but doesn't cover aspects like authentication needs, rate limits, error handling, or what 'detailed information' includes. For a tool with no annotations, this is a significant gap in transparency.

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 with no wasted words. It's front-loaded with the core purpose, making it easy to parse quickly. Every part of the sentence contributes directly to understanding the tool's function.

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 that an output schema exists, the description doesn't need to explain return values. However, with no annotations, 2 parameters (one undocumented in schema), and moderate complexity (fetching detailed data), the description is incomplete—it lacks behavioral context and parameter details, though the output schema mitigates some gaps.

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 0%, so the schema provides no parameter details. The description mentions 'detailed information' and implies a request ID is needed, but doesn't explain the 'include_body' parameter or its default value. It adds minimal semantic value beyond what's inferred from the tool name and schema structure.

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 ('detailed information for a single request'), making the purpose understandable. However, it doesn't differentiate from sibling tools like 'list_requests' or 'search_requests' beyond specifying 'single request,' which is somewhat implied by those names too.

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, such as needing a request ID, or compare it to siblings like 'list_requests' for multiple requests or 'search_requests' for filtering. This leaves the agent without explicit usage context.

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