Skip to main content
Glama
Sign In
CONTRI

CONTRI

by alphasafal
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Sign out of GitHub

sign_out
DestructiveIdempotent

Clears saved sign-in credentials and removes their stored copy so the current session is forgotten. Remove any GITHUB_TOKEN from the MCP config separately.

Instructions

Forgets the sign_in credential, including the saved copy. A GITHUB_TOKEN in the MCP config must be removed there.

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": "sign_out"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true and idempotentHint=true; the description adds the specific blast radius ('including the saved copy') and, importantly, the scope limit that a config-level GITHUB_TOKEN is untouched. That is real behavioral context beyond the annotations, though it does not say what happens when no credential is stored.

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?

Two short sentences, the primary effect front-loaded and the config caveat second. Every clause carries information; nothing is padding.

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?

With no parameters, no output schema, and annotations covering safety and idempotency, the definition supplies what an agent needs: what is erased and what is out of scope. Only the no-op case (signing out when nothing is stored) is left implicit, which the idempotent hint largely covers.

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 and the description correctly introduces none, so there is nothing to mis-specify. Baseline 4 applies for a parameterless tool.

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 gives a specific verb and object ('Forgets the sign_in credential, including the saved copy'), so an agent knows exactly what is removed. It is clearly the inverse of the sibling sign_in without naming it, though it does not explicitly contrast itself with other tools.

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?

Sign-out usage is self-evident and the description adds a genuine boundary condition: a GITHUB_TOKEN set in the MCP config must be removed there instead, telling the agent when this tool is insufficient. It stops short of explicit when-to-use/when-not phrasing, but for a zero-alternative operation this is solid guidance.

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

Deploy Server

Other Tools