scratch-unified-mcp

by blessed0x

Overview Schema Source Related Servers Discussions Admin

Python

Local

Social Set Active Session

social_set_active_session

Select a logged-in account to set as the active session, determining which account subsequent authenticated tools use.

Instructions

Choose which logged-in account subsequent authenticated tools act as.

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_set_active_session"
  }
}

Input Schema

Name	Required	Description	Default
`username`	Yes	Username of a session from `social_list_sessions`.

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Sep 19, 2026

TDQS

A3.6/5.0

Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states that it changes the active session for subsequent tools, but does not mention prerequisites (e.g., an existing session), reversibility, error conditions, or whether the change persists. For a state-changing tool, this is minimal and insufficient.

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 concise sentence that front-loads the core action and effect. It contains no filler or redundant information, making it appropriately sized and efficient.

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 setter with a single parameter and no annotations, the description covers the key aspects: what it does (chooses account), the scope (subsequent authenticated tools), and implicitly how to get the username (from social_list_sessions). The presence of an output schema likely covers return details, so nothing critical is missing.

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 schema already fully documents the single 'username' parameter with a description pointing to social_list_sessions, achieving 100% coverage. The description adds marginal context by clarifying that it refers to a logged-in account, but does not meaningfully enhance schema semantics. 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 clearly states the verb 'choose' and the resource 'active session', explaining that it selects which logged-in account subsequent authenticated tools act as. This distinguishes it from siblings like social_list_sessions (which lists sessions) and social_connect_session (which establishes a connection), leaving no ambiguity about its role.

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 description implies that this tool should be used after listing sessions (since the username comes from social_list_sessions) and that it affects subsequent authenticated tools. However, it does not explicitly mention alternatives or when not to use it, leaving some inference required. It gives clear context but no exclusions or direct comparison to siblings.

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

Deploy Server