msteams-personal-mcp

teams_logout

Deletes the saved personal Microsoft Teams sign-in from this machine, removing stored credentials to sign out or switch accounts.

Instructions

Delete the saved Teams personal sign-in from this machine.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "teams_logout"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.9.0Oct 23, 2026

TDQS

A3.6/5.0

Behavior3/5

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

With no annotations, the description carries the full disclosure burden. It usefully indicates a destructive action scoped to local storage ('from this machine'), which hints that server-side sessions or tokens may survive. It does not state reversibility, whether an active session is invalidated, or what errors occur when no sign-in exists.

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 sentence with no filler, front-loading the destructive verb and the affected resource. Nothing in it is redundant or restated from structured fields.

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?

For a zero-parameter, no-output-schema tool the description covers the core action, but a destructive unannotated tool should say more about effects: whether it clears only local credential cache or also signs out the live session, and whether it fails when not signed in.

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

Parameters4/5

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

The tool takes zero parameters, so the baseline is 4; there is nothing for the description to disambiguate. No parameter-level information is required or missing.

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 ('Delete') and a specific resource ('the saved Teams personal sign-in'), and adds the scope qualifier 'from this machine'. It is not tautological and clearly contrasts with the sibling teams_login, though it doesn't name that sibling explicitly.

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 intent to remove stored credentials is implied by 'Delete the saved ... sign-in', so an agent can infer this is the sign-out path. However, there is no explicit when-to-use guidance, no statement of prerequisites (must the user be signed in?), and no reference to teams_login or teams_status as alternatives.

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