Skip to main content
Glama

Capable

by run.capable
OverviewDiscussionsAdmin

Stop recording

stop_recording
Destructive

Pull the notetaker bot out of a call and cancel the recording. Use when a rep asks not to record a meeting the bot was scheduled for, or to remove it mid-call.

When to use: When a rep doesn't want a scheduled meeting recorded, or wants the bot removed mid-call.

Example: Don't record my 3pm — pull the bot off it.

Input Schema

NameRequiredDescriptionDefault
recording_idYesThe meeting recording's id — from record_meeting's result, or search_records({object_type:'meeting_recording'}) / get_record.

Output Schema

NameRequiredDescriptionDefault
recordingNoThe recording's full state — the same shape record_meeting returns as `recording`.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • removedInput schema / $schema
      Removed value: -"https://json-schema.org/draft/2020-12/schema"
  2. Changed1 schema field changed
    • removedInput schema / properties / recording_id / pattern
      Removed value: -"^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$"
  3. Changed6 schema fields changed
    • removedOutput schema / $schema
      Removed value: -"https://json-schema.org/draft/2020-12/schema"
    • removedOutput schema / additionalProperties
      Removed value: -{}
    • removedOutput schema / properties / recording / additionalProperties
      Removed value: -{}
    • addedOutput schema / properties / recording / description
      Added value: +"The recording's full state — the same shape record_meeting returns as `recording`."
    • removedOutput schema / properties / recording / properties
      Removed value: -{
-  "account_id": {
-    "anyOf": [
-      {
-        "format": "uuid",
-        "pattern": "^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$",
-        "type": "string"
-      },
-      {
-        "type": "null"
-      }
-    ]
-  },
-  "contact_id": {
-    "anyOf": [
-      {
-        "format": "uuid",
-        "pattern": "^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$",
-        "type": "string"
-      },
-      {
-        "type": "null"
-      }
-    ]
-  },
-  "created_at": {
-    "type": "string"
-  },
-  "id": {
-    "format": "uuid",
-    "pattern": "^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$",
-    "type": "string"
-  },
-  "meeting_platform": {
-    "anyOf": [
-      {
-        "type": "string"
-      },
-      {
-        "type": "null"
-      }
-    ]
-  },
-  "opportunity_id": {
-    "anyOf": [
-      {
-        "format": "uuid",
-        "pattern": "^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$",
-        "type": "string"
-      },
-      {
-        "type": "null"
-      }
-    ]
-  },
-  "scheduled_start": {
-    "anyOf": [
-      {
-        "type": "string"
-      },
-      {
-        "type": "null"
-      }
-    ]
-  },
-  "status": {
-    "type": "string"
-  },
-  "title": {
-    "anyOf": [
-      {
-        "type": "string"
-      },
-      {
-        "type": "null"
-      }
-    ]
-  },
-  "touch_id": {
-    "anyOf": [
-      {
-        "format": "uuid",
-        "pattern": "^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$",
-        "type": "string"
-      },
-      {
-        "type": "null"
-      }
-    ]
-  },
-  "transcript_text": {
-    "anyOf": [
-      {
-        "type": "string"
-      },
-      {
-        "type": "null"
-      }
-    ]
-  }
-}
    • removedOutput schema / properties / recording / required
      Removed value: -[
-  "id",
-  "status"
-]
  4. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, readOnlyHint=false, openWorldHint=true and idempotentHint=false, so the safety profile is largely covered by structured data. The description adds the scenario of mid-call removal, which is useful context, but it does not disclose what is destroyed (recording data, transcript), auth requirements, or reversibility beyond what annotations imply.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose is front-loaded, but the same usage guidance is stated three times: once in the opening sentence, again under 'When to use:', and a third time in the example ('Don't record my 3pm'). Two of the four sentences are near-verbatim duplicates and do not earn their place.

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 single-parameter tool with rich annotations and an output schema, the description need not explain return values, and it adequately covers purpose and trigger conditions. Only minor gaps remain around what exactly is torn down and whether the action is reversible.

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

Parameters3/5

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

Schema description coverage is 100% with a single well-documented recording_id parameter, so the schema carries the parameter semantics. The description mentions no parameter at all and adds no syntax or sourcing detail beyond the schema's own note about record_meeting and search_records. Baseline 3 applies.

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 names a specific verb and resource: 'Pull the notetaker bot out of a call and cancel the recording.' That is unambiguous about the action. It does not explicitly differentiate itself from adjacent siblings like record_meeting or share_recording, so it falls short of the 5 criterion.

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?

There is an explicit 'When to use' section covering the two scenarios (rep declines a scheduled recording, or wants the bot removed mid-call). It gives clear context but offers no when-not-to-use conditions and does not route to alternative tools for related operations.

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

All Capable toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources