Skip to main content
Glama
Sign In
cmcp

cmcp

by DeveshB-1
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Auth: Digest/DigestAuth Request

auth_digest_digestauth_request
Read-only

Triggers a Digest Auth challenge by requesting a protected endpoint, then extracts realm and nonce from the 401 response for hashing subsequent authenticated requests.

Instructions

Performing a simple GET request to this endpoint returns status code 401 Unauthorized with WWW-Authenticate header containing information to successfully authenticate subsequent requests. The WWW-Authenticate header must be processed to extract realm and nonce values to hash subsequent requests.

When this request is executed within Postman, the script attached with this request does the hard work of extracting realm and nonce from the header and set it as global variables named echo_digest_nonce and echo_digest_realm. These variables are re-used in subsequent request for seamless integration of the two requests.

(Postman request: Auth: Digest/DigestAuth Request | GET https://postman-echo.com/digest-auth)

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

Beyond the readOnly/openWorld annotations, it discloses the surprising behavior an agent must know: the call intentionally returns 401, the script mutates global state (echo_digest_nonce, echo_digest_realm), and those values are prerequisites for the next call. It does not describe failure modes if the script/Postman environment is absent.

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 opening sentence about the 401 and required header processing is well front-loaded, but the Postman-runtime explanation and the raw request/URL line are verbose for what is essentially one HTTP call, and the global-variable mechanism is Postman-specific rather than general.

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?

With no output schema, the description does cover the salient return shape (401 + WWW-Authenticate) and the side effects, which is what an agent needs to chain requests. It stops short of stating what a successful full digest flow looks like or that the second tool is required, but for a 0-param demo endpoint this is largely sufficient.

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?

Zero parameters, so there is nothing to disambiguate; baseline 4 applies. The description does not mislead about inputs.

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 states concretely what the call does — issues a GET that returns 401 Unauthorized with a WWW-Authenticate header, whose realm/nonce are parsed and stored as global variables for the follow-up request. That is more specific than the name alone and implicitly delineates it from auth_digest_digestauth_success, though it never names that sibling outright.

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

Usage Guidelines3/5

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

It says the variables are 're-used in subsequent request for seamless integration of the two requests', which implies this is the first leg of a two-step flow, but it never explicitly says 'call this before auth_digest_digestauth_success' or what happens if you skip it.

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