Skip to main content
Glama
Sign In
cmcp

cmcp

by DeveshB-1
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Request Methods/PATCH Request

request_methods_patch_request
Destructive

Send an HTTP PATCH request to update a resource and return debug details such as headers, query parameters, and the request body for inspection.

Instructions

The HTTP PATCH method is used to update resources on a server. The exact use of PATCH requests depends on the server in question. There are a number of server implementations which handle PATCH differently. Technically, PATCH supports both Query String parameters and a Request Body.

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

(Postman request: Request Methods/PATCH Request | PATCH https://postman-echo.com/patch)

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_patch_request"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyNoRaw request body.Curabitur auctor, elit nec pulvinar porttitor, ex augue condimentum enim, eget suscipit urna felis quis neque. Suspendisse sit amet luctus massa, nec venenatis mi. Suspendisse tincidunt massa at nibh efficitur fringilla. Nam quis congue mi. Etiam volutpat.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.8/5.0
Behavior3/5

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

The annotations already declare openWorldHint=true, destructiveHint=true, and readOnlyHint=false. The description adds that the endpoint returns debug information such as headers, query arguments, and body, but it also opens with generic PATCH semantics that could imply real resource mutation without clarifying that this particular endpoint is an echo/debug service.

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

Conciseness2/5

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

The description spends most of its space on generic HTTP PATCH background before reaching the specific endpoint behavior. It is not tightly front-loaded and contains material that does not directly help invoke this particular tool.

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?

For a simple echo-style endpoint with no output schema, the description sufficiently states the request verb and the kind of debug information returned. It stops short of describing the response structure or clarifying the safety behavior relative to the destructive annotation.

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

Parameters2/5

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

Schema description coverage is 100% for the single body parameter, so the schema itself is clear. However, the description mentions that PATCH technically supports Query String parameters, which are not represented in the input schema, potentially misleading an agent into supplying unsupported parameters.

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 names the HTTP PATCH method and states that the endpoint accepts a PATCH request and returns debug information such as headers, query arguments, and body. This is specific enough to identify the tool, though it does not explicitly contrast it with sibling request-method tools.

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 gives a generic explanation of what HTTP PATCH is, but provides no guidance on when to use this tool instead of siblings like GET, POST, PUT, or DELETE. It also does not state prerequisites or conditions for choosing this endpoint.

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