cmcp

Overview Schema Source Related Servers Discussions Admin

Request Methods/DELETE Request

request_methods_delete_request

Destructive

The HTTP DELETE method is used to delete resources on a server. The exact use of DELETE requests depends on the server implementation. In general, DELETE requests support both, Query String parameters as well as a Request Body.

Instructions

This endpoint accepts an HTTP DELETE request and provides debug information such as the HTTP headers, Query String arguments, and the Request Body.

(Postman request: Request Methods/DELETE Request | DELETE https://postman-echo.com/delete)

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

Input Schema

Name	Required	Description	Default
`body`	No	Raw request body.	Donec fermentum, nisi sed cursus eleifend, nulla tortor ultricies tellus, ut vehicula orci arcu ut velit. In volutpat egestas dapibus. Morbi condimentum vestibulum sapien. Etiam dignissim diam quis eros lobortis gravida vel lobortis est. Etiam gravida sed.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 1, 2026

TDQS

B3.2/5.0

Behavior3/5

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

Annotations already declare destructiveHint=true, readOnlyHint=false, and openWorldHint=true. The description adds useful context that query string parameters and a request body are supported and that the response contains debug information, but it does not reconcile the destructive annotation with the echo/debug nature of the endpoint or clarify that no real resource is deleted.

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

Conciseness3/5

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

The description is reasonably sized but begins with generic HTTP DELETE education before reaching the endpoint-specific behavior. The Postman request line is helpful, though the first paragraph could be trimmed to focus more quickly on what this tool does.

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 one-parameter echo endpoint with full schema coverage and annotations covering the safety profile, the description provides enough context: the HTTP method, the endpoint URL, supported inputs, and the debug-style return. It only misses an explicit note about the echo nature of the endpoint.

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 coverage is 100% and the single body parameter is already described as 'Raw request body.' The description adds that DELETE requests may carry query string parameters and a request body, but does not provide additional syntax or format guidance beyond the schema.

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 identifies the HTTP method and endpoint behavior: it accepts a DELETE request and returns debug information such as headers, query arguments, and body. It does not explicitly distinguish itself from sibling GET/POST/PUT/PATCH tools, but the method-specific naming and endpoint URL make the purpose unambiguous.

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 explains general HTTP DELETE semantics but gives no explicit guidance on when to use this endpoint versus the sibling request-method endpoints. There are no exclusions or prerequisites, leaving the agent to infer that this is the DELETE-specific echo endpoint.

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