Skip to main content
Glama
Sign In

SurveyNinja

by io.surveyninja
OverviewDiscussionsAdmin

Account sessions

manage_user_sessions
Destructive

Active sign-ins to the account: where the person is still logged in, and closing an unwanted one. Shows the device, browser, city and when it was last used. Note: close_all closes EVERY browser sign-in, including the one the person is working in right now — in the cabinet that button keeps the current session, but here there is no current session because the assistant works by key. That is why close_all needs a confirmation.

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": {
      "action": "<action>"
    },
    "name": "manage_user_sessions"
  }
}

Input Schema

NameRequiredDescriptionDefault
actionYesWhat to do: list, close (one sign-in), close_all.
session_idNoSign-in id from list. Required for close.
confirm_close_allNoConfirmation for close_all: the person will be signed out of the cabinet they are working in.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior5/5

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

Beyond the destructiveHint annotation, the description explains exactly why close_all is dangerous: it signs out every browser session, including the one the person is actively using, because the assistant has no 'current session' of its own. This is critical behavioral context that an agent would not get from annotations alone and directly justifies the confirmation parameter.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose is front-loaded and most sentences carry useful information. The explanation of the cabinet-versus-assistant session distinction is slightly wordy, but it earns its place by clarifying why confirmation is required.

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?

The description covers what list returns (device, browser, city, last used), the scope of close, and the destructive nature of close_all. No output schema exists, so describing list fields is valuable, though it does not describe what a close or close_all response looks like.

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 coverage is 100%, so the schema already documents action, session_id, and confirm_close_all. The description mostly reinforces the close_all behavior and confirmation requirement rather than adding new syntactic or semantic detail beyond the schema. Baseline 3 is appropriate.

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 resource (active sign-ins / sessions) and the available operations (listing, closing one, closing all). It does not explicitly differentiate from any sibling tool, but there is no direct session-management sibling, so the purpose is still easy to identify.

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?

Usage is implied through the actions: list sessions, close a specific session, or close all sessions. The description does not explicitly say to call list first to obtain a session_id, nor does it state when not to use the tool. The close_all caveat adds useful context but is not framed as explicit usage guidance.

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

All SurveyNinja toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources