Skip to main content
Glama
tachote
by tachote

Deregister session

deregister_interactsh_session

Remove a session from interactsh and local cache to clean up resources after completing out-of-band interaction testing for security workflows.

Instructions

Removes a session from interactsh and local cache.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
correlation_idYes

Implementation Reference

  • src/server.js:377-388 (registration)
    Registration of the 'deregister_interactsh_session' MCP tool, including title, description, input schema, and inline handler function.
    server.registerTool(
      'deregister_interactsh_session',
      {
        title: 'Deregister session',
        description: 'Removes a session from interactsh and local cache.',
        inputSchema: { correlation_id: z.string() },
      },
      async ({ correlation_id }) => {
        await service.deregisterSession(correlation_id);
        return result({ status: 'deregistered', correlation_id });
      },
    );
  • Inline handler function for the tool that invokes the service's deregisterSession method and returns a success result.
    async ({ correlation_id }) => {
      await service.deregisterSession(correlation_id);
      return result({ status: 'deregistered', correlation_id });
    },
  • Input schema definition using Zod: requires a 'correlation_id' string.
    inputSchema: { correlation_id: z.string() },
  • Core helper method in InteractshService class that performs the deregistration by POSTing to interactsh /deregister endpoint with session credentials and removes the session from local Map cache.
    async deregisterSession(correlationId) {
      const session = this.#requireSession(correlationId);
      const url = new URL('/deregister', this.baseUrl);
    
      await this.#request(url, {
        method: 'POST',
        headers: { 'content-type': 'application/json' },
        body: JSON.stringify({
          'correlation-id': session.correlationId,
          'secret-key': session.secretKey,
        }),
      });
    
      this.sessions.delete(correlationId);
    }
Behavior2/5

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

With no annotations, the description carries the full burden of behavioral disclosure. It states the tool removes a session from both interactsh and local cache, implying a destructive operation, but doesn't clarify if this is irreversible, requires specific permissions, or has side effects (e.g., affecting ongoing interactions). More details on consequences or limitations are needed for a higher score.

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, clear sentence with no wasted words. It's front-loaded with the core action and efficiently conveys the essential information without unnecessary elaboration, making it highly concise and well-structured.

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 tool's destructive nature (implied by 'Removes'), lack of annotations, no output schema, and incomplete parameter documentation, the description is insufficient. It doesn't address what happens post-deregistration, error conditions, or provide enough context for safe and effective use, leaving significant gaps for an AI agent.

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?

The description doesn't mention the parameter 'correlation_id', and schema description coverage is 0%, so it adds no semantic information beyond the schema. However, with only one parameter, the baseline is 3, as the schema alone might suffice for a simple input, but the description fails to compensate for the lack of schema descriptions.

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 ('Removes') and the target ('a session from interactsh and local cache'), making the purpose understandable. However, it doesn't explicitly differentiate from sibling tools like 'list_interactsh_sessions' or 'poll_interactsh_session' beyond the obvious action difference, which prevents a perfect score.

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?

No guidance is provided on when to use this tool versus alternatives. For example, it doesn't mention prerequisites (e.g., requiring an existing session) or warn against misuse (e.g., deregistering active sessions). The description lacks context about its role relative to siblings like 'create_interactsh_session'.

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/tachote/mcp-interactsh'

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