Skip to main content
Glama
SoManyLemons MCP

SoManyLemons MCP

Official
by NoMiddleInc

Get recording

get_recording
Read-onlyIdempotent

Retrieve one recording and its clips with live scheduling status to check what is ready to publish; the lookup is read-only and requires the recording ID.

Instructions

One recording and its clips with their live scheduling status. Reads only.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "recording_id": "<recording_id>"
    },
    "name": "get_recording"
  }
}

Input Schema

NameRequiredDescriptionDefault
account_idNo
recording_idYesThe recording's id, from list_recordings.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.9.36

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so 'Reads only.' merely restates structured data. The description does add a genuine behavioral detail — that clips are returned with their *live* scheduling status — but says nothing about what happens for an unknown or inaccessible recording_id, nor whether clips are paginated or truncated.

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?

Two short sentences with the resource and payload front-loaded; nothing is buried. The trailing 'Reads only.' is mildly redundant with the readOnlyHint annotation but costs only three words.

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?

With no output schema, the description carries the burden of describing returns, and it does so only in outline: one recording, its clips, and live scheduling status. It omits error behavior for invalid ids and whether clip lists are bounded, which an agent would want before calling.

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 coverage is roughly 50%, and both visible parameters (recording_id sourced from list_recordings, account_id for multi-account teammates) are already documented in the schema. The description adds no additional meaning about parameter values, formats, or edge cases, so the baseline of 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 the resource (one recording) and the payload (its clips with live scheduling status), which tells an agent more than the title alone. It does not distinguish this from the similar-looking sibling show_recording or explain how it differs from list_recordings, so it stops short of full sibling differentiation.

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 when-to-use guidance: nothing says to call this when you already have a recording id, or to use list_recordings first, or how it relates to show_recording. The only routing hint ('from list_recordings') lives in the input schema, not the description.

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