Skip to main content
Glama
godzeo
by godzeo

http_delete

Send a full-featured HTTP DELETE request with headers, cookies, body, and timeout support. Log all request details for security testing, API testing, or web automation.

Instructions

HTTP DELETE request with full support (headers, cookies, body, timeout) - All requests logged

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bodyNo
cookiesNo
headersNo
timeoutNo
urlYes

Implementation Reference

  • The http_delete tool handler function, decorated with @mcp.tool() for registration. Executes DELETE request via shared helper function.
    @mcp.tool()
    def http_delete(
        url: str, 
        headers: Optional[Dict[str, str]] = None,
        cookies: Optional[Dict[str, str]] = None,
        body: Optional[str] = None,
        timeout: float = 30.0
    ) -> str:
        """HTTP DELETE request with full support (headers, cookies, body, timeout) - All requests logged"""
        try:
            result = make_http_request_with_logging("DELETE", url, headers or {}, cookies or {}, body or "", timeout)
            return json.dumps(result, indent=2)
        except Exception as e:
            return f"Error: {str(e)}"
  • Shared helper function that performs the actual HTTP request using httpx, logs via log_request_response, and returns detailed response info. Used by http_delete.
    def make_http_request_with_logging(method: str, url: str, headers: dict, cookies: dict, body: str, timeout: float):
        """Universal HTTP request function with logging"""
        try:
            with httpx.Client(timeout=timeout) as client:
                response = client.request(
                    method=method.upper(),
                    url=url,
                    headers=headers,
                    cookies=cookies,
                    content=body.encode('utf-8') if body else None
                )
                
                # Log the request and response
                log_path = log_request_response(
                    method=method.upper(), 
                    url=url, 
                    headers=headers, 
                    cookies=cookies, 
                    body=body,
                    status_code=response.status_code,
                    response_headers=dict(response.headers),
                    response_content=response.text,
                    response_length=len(response.text)
                )
                
                return {
                    "method": method.upper(),
                    "url": url,
                    "status_code": response.status_code,
                    "response_headers": dict(response.headers),
                    "response_content": response.text,
                    "response_length": len(response.text),
                    "request_headers": headers,
                    "request_cookies": cookies,
                    "request_body": body,
                    "logged_to": log_path
                }
        except Exception as e:
            # Log the error
            log_request_response(
                method=method.upper(), url=url, headers=headers, cookies=cookies, body=body,
                status_code=0, response_headers={}, response_content="", response_length=0,
                error=str(e)
            )
            raise e
  • Utility function to log full request/response details to file, used by HTTP request helper.
    def log_request_response(method: str, url: str, headers: dict, cookies: dict, body: str, 
                            status_code: int, response_headers: dict, response_content: str, 
                            response_length: int, error: str = None):
        """Log complete request and response details"""
        log_data = {
            "timestamp": datetime.datetime.now().isoformat(),
            "request": {
                "method": method,
                "url": url,
                "headers": headers,
                "cookies": cookies,
                "body": body,
                "body_length": len(body) if body else 0
            },
            "response": {
                "status_code": status_code if not error else "ERROR",
                "headers": response_headers if not error else {},
                "content_length": response_length if not error else 0,
                "content_preview": response_content[:500] + "..." if response_content and len(response_content) > 500 else response_content
            },
            "error": error
        }
        
        logger.info(f"HTTP_REQUEST: {json.dumps(log_data, indent=2, ensure_ascii=False)}")
        return log_path
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It mentions that 'All requests logged,' which adds some context about side effects. However, it doesn't cover critical aspects like authentication requirements, rate limits, error handling, or what 'DELETE' actually does to the target resource (destructive nature).

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, efficient sentence that front-loads the core purpose. Every phrase ('HTTP DELETE request,' 'full support,' 'All requests logged') contributes meaningful information without waste.

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

Completeness2/5

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

For a 5-parameter tool with no annotations and no output schema, the description is incomplete. It lacks details on authentication, error responses, the destructive nature of DELETE, and how to interpret results. The logging mention is helpful but insufficient for full contextual understanding.

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 description must compensate. It lists 'headers, cookies, body, timeout' as supported features, which maps to 4 of the 5 parameters (missing 'url'). This adds some meaning beyond the bare schema, but doesn't explain parameter purposes, formats, or constraints in detail.

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 tool performs an 'HTTP DELETE request' with 'full support' for various HTTP features, which is a specific verb+resource combination. However, it doesn't explicitly distinguish this DELETE operation from its sibling tools (GET, HEAD, OPTIONS, etc.) beyond the HTTP method name.

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 DELETE request versus alternatives like http_raw_request or other HTTP methods. It mentions 'full support' but doesn't specify use cases, prerequisites, or exclusions for DELETE operations.

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

Related 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/godzeo/mcp-requests'

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