Skip to main content
Glama
SunLicense MCP server

SunLicense MCP server

Official

sign_out_member

DestructiveIdempotent

Sign a team member out everywhere to end their sessions and require sign-in again, useful when an unauthorized sign-in is suspected. Confirm with the user before signing out.

Instructions

Sign a team member out everywhere: their sessions end and they have to sign in again. For a sign-in that wasn't theirs. Confirm with the user first.

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": {
      "member": "<member>"
    },
    "name": "sign_out_member"
  }
}

Input Schema

NameRequiredDescriptionDefault
memberYesthe member's user id or email

Output Schema

NameRequiredDescriptionDefault
noteYes
memberYes
resultNowhat SunLicense answered

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, so the description's added value is the concrete effect: all sessions end and the member must sign in again. It also adds a behavioral requirement not encoded anywhere in structured fields — confirm with the user before calling. It does not mention whether access is revoked permanently or any rate/audit implications, keeping it short of a 5.

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?

Three short sentences: effect first, use case second, safety instruction last. Every sentence carries distinct information and nothing is redundant.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a one-parameter mutation with an output schema and full annotation coverage, the description supplies what remains: the blast radius (all sessions), the recovery consequence (must sign in again), the intended scenario, and the confirmation step. An agent has everything needed to decide and invoke correctly.

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% and the single parameter already documents that it accepts a user id or email. The description only reinforces that the target is a team member, adding no syntax or format detail beyond the schema, so the baseline of 3 applies.

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 and resource ('sign a team member out') plus a scope qualifier ('everywhere') that distinguishes it from any per-session sign-out. The phrasing 'For a sign-in that wasn't theirs' hints at the security use case but is slightly oblique as a purpose statement.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives a clear triggering condition ('for a sign-in that wasn't theirs') and an explicit prerequisite ('Confirm with the user first'). It does not name an alternative tool, but no sibling in the catalog appears to be a competing sign-out/revoke-session operation, so the guidance is sufficient.

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