Skip to main content
Glama
Sign In
scratch-unified-mcp

scratch-unified-mcp

by blessed0x
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Social Forget Session

social_forget_session

Remove a stored user session from the server and disk. Optionally invalidate the session ID on Scratch to log out all clients using it.

Instructions

Drop a session from this server and from the on-disk store.

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": {
      "username": "<username>"
    },
    "name": "social_forget_session"
  }
}

Input Schema

NameRequiredDescriptionDefault
logoutNoAlso invalidate the session id server-side on Scratch. This breaks any other client using the same session id, including the user's browser if the login came from there.
usernameYesUsername of the session to remove.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the behavioral disclosure burden. It does reveal that the session is removed from both the server and the on-disk store, which is useful. However, it does not state irreversibility, required permissions, or consequences for active clients; the logout parameter description partially covers server-side invalidation.

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 one front-loaded sentence with no filler: it names the action, the resource, and the two affected storage locations. Every word earns its place.

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?

The tool is simple, has only two well-documented parameters, and has an output schema, so the core invocation details are present. The main gap is the lack of usage guidance and side-effect disclosure beyond the literal removal, but the low complexity keeps the shortcoming moderate.

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%, and both parameters ('username' and 'logout') already have detailed schema descriptions. The tool description adds no additional meaning beyond what the schema provides, so baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses the specific verb 'Drop' with the resource 'a session' and states the scope ('from this server and from the on-disk store'), making the operation distinct from siblings like social_connect_session, social_list_sessions, social_set_active_session, and social_verify_session. It is immediately clear what this tool does.

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 explains when to use this tool versus alternatives such as social_verify_session or social_set_active_session, and there is no mention of when-not-to-use or prerequisites. The usage must be inferred entirely from the name and short description.

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