Skip to main content
Glama
Gong MCP

Gong MCP

by tadnir

gong_login

Get the link to sign in to Gong and authorize access to your call data; returns your current status when already signed in. Use it to start or check your session before reading calls.

Instructions

Get the link where the user signs in to Gong (Gong's own sign-in and the company's SSO run on that page, never in the chat). Returns the status when already signed in.

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_login"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

No annotations are provided, so the description must carry the full behavioral burden, and it does usefully: it discloses that sign-in (both Gong-native and SSO) occurs on the linked page and never in the chat, which is a security-relevant constraint, and that the tool returns a status when a session already exists. It does not say whether the link is single-use or how long it remains valid.

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?

It is two short sentences with no filler, and the key constraint is front-loaded in the parenthetical. Minor awkwardness comes from the nested 'Gong (~Gong's own~)' phrasing, but no sentence is wasted.

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?

For a zero-parameter authentication-links tool with no output schema, the description covers what the agent needs: what it returns, where sign-in happens, and the already-signed-in case. Link lifetime and the exact status shape remain unspecified, but those are secondary.

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 to document beyond the return behavior, which the description does address.

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 has a specific verb-plus-resource: it returns the URL where the user signs in to Gong. It also states an important scope constraint: authentication happens on the Gong page, not in the chat. It does not name gong_session_status, which covers the 'already signed in' case, so an agent could still hesitate between this tool and that sibling.

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?

The definition makes the context clear: use it when the user must sign in, and send them to the returned page rather than handling credentials in the chat. It does not explicitly direct the agent to gong_session_status or gong_logout, and that leaves the branch for an already-signed-in user implicit.

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