Skip to main content
Glama

delete_state

Delete and clear a specific stateful session entry from Redis for a project workspace. Use this tool to reset a stateful test flow back to a clean initial state (e.g. before re-running a multi-step registration or payment scenario) without waiting for the 15-minute Redis TTL to expire.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "projectSlug": "<projectSlug>",
      "sessionKey": "<sessionKey>"
    },
    "name": "delete_state"
  }
}

Input Schema

NameRequiredDescriptionDefault
sessionKeyYesExact session key to remove from Redis.
projectSlugYesUnique slug of the project workspace (obtain from list_projects).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / projectSlug / description
      Previous value: -"Project slug"New value: +"Unique slug of the project workspace (obtain from list_projects)."
    • changedInput schema / properties / sessionKey / description
      Previous value: -"Session key to delete"New value: +"Exact session key to remove from Redis."
  2. First observed

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations, the description has to carry the full behavioral burden. It does disclose that the operation removes data from Redis and that entries otherwise expire via a 15-minute TTL, which conveys destructiveness and the reason to use it. It does not say whether the delete is idempotent, what happens when the sessionKey does not exist, whether an error is returned, or whether the deleted data can be recovered.

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?

Two sentences with no filler; the operation and its target are front-loaded, followed by the motivating scenario. The parenthetical example and TTL detail each earn their place by clarifying intent.

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 simple two-parameter tool with no output schema and no annotations, the description covers what it does, why to use it, and the TTL behavior that motivates it. The remaining gap is error/edge-case behavior on a missing key, which is minor but would be needed for full confidence.

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 100%, so both sessionKey and projectSlug are already documented in the schema, including the hint to obtain the slug from list_projects. The description only reinforces the project-workspace scoping and adds no format or validity details beyond the schema, so the baseline of 3 applies.

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 gives a specific verb and resource: "Delete and clear a specific stateful session entry from Redis for a project workspace." That distinguishes it in substance from set_state and get_state through the verb, though it never names those siblings explicitly, so an agent must infer the routing.

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

Usage Guidelines4/5

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

It states a concrete when-to-use case: reset a stateful test flow to a clean initial state before re-running a multi-step registration or payment scenario. It offers no explicit when-not guidance (e.g. use set_state to overwrite rather than clear, or whether this is safe to call on a missing key), but the usage context is clear enough to act on.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources