Skip to main content
Glama
Gong MCP

Gong MCP

by tadnir

gong_logout

Sign out of the saved Gong session to remove stored sign-in data from your machine. Use it when you need to end Gong access or switch accounts.

Instructions

Forget the Gong session saved here.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations, the description must carry the behavioral load; it does disclose the key fact that the locally saved session is what gets destroyed. It does not say whether the server-side token is revoked, whether it fails if no session exists, or whether the effect is reversible.

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?

A single front-loaded sentence with no filler. It is arguably a touch too terse for a credential-clearing operation, but nothing is wasted.

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?

Complexity is low (no params, no output schema, no annotations), yet for a session-destroying tool the description leaves open whether logout is server-side, what error occurs with no active session, and what the caller should do next. Adequate but not complete.

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 there is nothing for the description to disambiguate; baseline applies. "Saved here" usefully hints that state lives in the local MCP environment rather than a remote actor.

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?

"Forget the Gong session saved here" names a concrete resource (the stored Gong session) and implies the inverse of the sibling gong_login, so an agent can place it in the auth lifecycle. "Forget" is metaphorical rather than a precise verb like "clear" or "log out," which keeps it short of a 5.

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

Usage Guidelines2/5

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

There is no explicit statement of when to call this (e.g., after finishing work, before switching accounts) and no reference to gong_session_status or gong_login as alternatives. Usage is only inferable from the name and the word "Forget."

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