Skip to main content
Glama
SoManyLemons MCP

SoManyLemons MCP

Official
by NoMiddleInc

Finish recording upload

finish_recording_upload
Idempotent

Saves an uploaded in-chat recording as a new recording and starts editing it, so recorder workflows can finalize uploads and continue in the editor.

Instructions

Saves a take the in-chat recorder uploaded as a new recording and starts editing it. Counts against the account's recording allowance. Called by the recorder itself.

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": {
      "upload_id": "<upload_id>",
      "idempotency_key": "<idempotency_key>"
    },
    "name": "finish_recording_upload"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleNo
upload_idYes
account_idNo
instructionNo
idempotency_keyYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.9.36

TDQS

A4/5.0
Behavior4/5

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

Goes beyond the annotations by disclosing that the call consumes the account's recording allowance and spawns an editing session — non-obvious side effects and quota costs. It also corroborates the idempotentHint with the required idempotency_key, though it says nothing about failure modes when the allowance is exhausted.

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?

Three short sentences, front-loaded with the action, then the cost, then the caller constraint. No filler or restatement of the name.

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?

For a mutation with quota impact, five undocumented parameters, and no output schema, the description is thin: it doesn't say what is returned, what happens on a duplicate idempotency key, or what title/instruction do. Annotations carry idempotency and safety, but parameter behavior is a real gap.

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 0% and the description explains none of the five parameters: upload_id, idempotency_key, title, instruction, and account_id are left entirely to their titles. Only the vague phrase 'a take the in-chat recorder uploaded' gestures at upload_id.

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?

States a specific verb and resource: saves an uploaded take as a new recording and starts editing it. That distinguishes it from create_recording_upload and add_recording, though the description never names those siblings explicitly.

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

Usage Guidelines3/5

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

'Called by the recorder itself' implies this is normally invoked by the in-chat recorder rather than by an agent, which is genuine usage context. But it doesn't say what an agent should do instead (e.g., create_recording_upload or add_recording) or under what conditions a direct call is appropriate.

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