Skip to main content
Glama
hofill
by hofill

delete_all_requests

Remove all stored HTTP requests and DNS records from the current session to clear data and manage storage.

Instructions

Delete all requests for the current session.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
confirmYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The main handler logic for delete_all_requests in RequestrepoMCPService class. Validates confirmation via _require_confirm, calls the underlying client's delete_all_requests method, and returns the result.
    def delete_all_requests(self, *, confirm: bool) -> dict[str, Any]:
        self._require_confirm(confirm, "delete_all_requests")
        deleted = self._client().delete_all_requests()
        return {"deleted": deleted}
  • MCP tool registration using @mcp.tool() decorator. Exposes the delete_all_requests function to the MCP server with a docstring describing its purpose.
    @mcp.tool()
    def delete_all_requests(confirm: bool) -> dict[str, Any]:
        """Delete all requests for the current session."""
        return resolved_service.delete_all_requests(confirm=confirm)
  • Helper method _require_confirm used by delete_all_requests to enforce confirmation safety check for destructive operations.
    @staticmethod
    def _require_confirm(confirm: bool, action: str) -> None:
        if not confirm:
            raise ValueError(f"{action} is destructive and requires confirm=true.")
  • Test mock implementation of delete_all_requests in FakeClient class used for unit testing the service logic.
    def delete_all_requests(self) -> bool:
        self.delete_all_called = True
        return True
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 the action is a deletion but doesn't specify if it's reversible, requires specific permissions, affects other data, or has rate limits. The description adds minimal context beyond the basic action, leaving critical behavioral traits undocumented.

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, direct sentence with zero waste. It's appropriately sized and front-loaded, clearly stating the tool's purpose without unnecessary elaboration. Every word earns its place, making it highly efficient.

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?

Given the complexity of a destructive operation with no annotations and an output schema (which isn't described in the description), the description is incomplete. It doesn't explain the irreversible nature, session dependency, or what the output might contain. For a tool that deletes all requests, this lack of context is a significant gap.

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?

With 1 parameter and 0% schema description coverage, the description doesn't mention the 'confirm' parameter at all. However, since there are 0 parameters described in the schema, the baseline is 4. The description fails to compensate for the lack of parameter documentation, but the low parameter count keeps it from scoring lower.

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 action ('Delete') and resource ('all requests for the current session'), providing a specific verb+resource combination. However, it doesn't explicitly differentiate from sibling tools like 'delete_request' (which deletes individual requests) or 'list_requests' (which lists them), missing full sibling differentiation.

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 (e.g., needing an active session), exclusions (e.g., irreversible action), or compare to siblings like 'delete_request' for selective deletion or 'list_requests' for verification. Usage is implied only by the tool name and description.

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/hofill/RequestRepo-MCP'

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