digikala-mcp

Logout Account

logout_account

End the current account session using its session token while leaving other account sessions active.

Instructions

Discard this host tool session without affecting other accounts.

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": {
      "session_token": "<session_token>"
    },
    "name": "logout_account"
  }
}

Input Schema

Name	Required	Description	Default
`session_token`	Yes

Output Schema

Name	Required	Description	Default
`disconnected`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 28, 2026

TDQS

B3.3/5.0

Behavior3/5

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

Annotations only declare readOnlyHint=false and openWorldHint=false, a minimal safety profile. The description usefully adds the blast radius ('without affecting other accounts'), but says nothing about whether the session token is invalidated server-side, whether the action is reversible, or what auth state remains.

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?

A single tight sentence with the action front-loaded and the scoping caveat immediately after; 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?

An output schema exists, so return values need no explanation, and the safety annotations are thin. Still, the undocumented required token and the absence of any session-invalidation or permission detail leave gaps for an agent invoking a state-changing tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

There is one required parameter (session_token) with 0% schema description coverage, so the schema supplies nothing. The description never mentions the token, where it comes from, or its format, so it fails to compensate for the schema gap.

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?

States a specific verb (discard) and resource (this host tool session), and the qualifier 'without affecting other accounts' scopes the effect. It is distinguishable from login_account and the cart siblings, though it does not explicitly name a contrasting sibling.

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?

The purpose implies the use case (ending the current host session) but there is no explicit when-to-use guidance, no prerequisites, and no statement of what to do instead if the intent is to log out other accounts.

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

Deploy Server