Skip to main content
Glama

Gong

by io.github.pipeworx-io

Recall

recall
Read-onlyIdempotent

Retrieve a value previously saved via remember, or list all saved keys (omit the key argument). Use to look up context the agent stored earlier — the user's target ticker, an address, prior research notes — without re-deriving it from scratch. Scoped to your identifier (anonymous IP, BYO key hash, or account ID). Pair with remember to save, forget to delete.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
keyNoMemory key to retrieve (omit to list all keys)

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "key": "user_research_topic"
+  },
+  {}
+]
  2. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already mark readOnlyHint, idempotentHint, and destructiveHint, so the description carries a low burden. It adds valuable behavioral context: listing keys when omitted, scoping to an identifier, and pairing with remember/forget. No contradictions with annotations.

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 sentences packed with essential information: main action, usage guidance, scope, and pairing. No fluff; every sentence earns its place. The most critical action is front-loaded.

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?

Given the tool's simplicity (one optional parameter, strong annotations, no output schema needed), the description covers all necessary aspects: what it does, when to use it, parameter behavior, and implications (scope). No gaps.

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

Parameters5/5

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

Schema coverage is 100%, but the description adds meaning beyond the schema: it explains that omitting the key lists all saved keys. This directly aids the agent in understanding the parameter's optionality and effect.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses specific verbs ('Retrieve', 'list') and resources ('value previously saved via remember', 'all saved keys'). It clearly distinguishes itself from sibling tools like 'remember' and 'forget' by stating its retrieval function and the option to list keys.

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 description explicitly states when to use the tool: 'Use to look up context the agent stored earlier...without re-deriving it from scratch.' It also mentions pairing with 'remember' and 'forget', providing context for its place among siblings. However, it does not explicitly state when not to use or provide alternatives.

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

All Gong toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.9/5.0
Disambiguation4/5

Most tools have distinct purposes due to detailed descriptions, but there is potential confusion among the many Polymarket and pipeworx-related tools. The Gong-specific tools are clearly separated.

Naming Consistency3/5

Naming conventions are mixed: some use snake_case, others camelCase, and there is inconsistency between groups (e.g., gong_* vs. polymarket_*). However, within each subgroup, naming is consistent.

Tool Count2/5

35 tools is high for coherence. The server covers multiple domains (Gong calls, data research, betting), leading to an overloaded toolset that could be streamlined into fewer, more general tools.

Completeness4/5

The toolset is comprehensive for its intended use cases, covering Gong call management, a wide array of data lookups, and Polymarket betting analysis. Minor gaps exist, such as limited CRM features beyond calls.

Resources