Skip to main content
Glama
SoManyLemons MCP

SoManyLemons MCP

Official
by NoMiddleInc

Record in chat

record_in_chat
Read-onlyIdempotent

Open an in-chat recorder to capture a new video or audio take; once the user records and confirms, the take is saved and edited into clips.

Instructions

Shows a recorder inside the chat for recording a new video or audio take with the camera and microphone. The user presses record, then Use this recording; the take is saved to their account and edited into clips. The recorder shows editing progress, plays the finished clips and reports the recording's id back. Calling this records nothing by itself.

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": "record_in_chat"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleNo
account_idNo
instructionNoOptional guidance for the edit, such as which topics to cut clips from.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.9.36

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, and the description usefully reconciles that with the appearance of persistence by noting the save and edit happen after user interaction, not on call. It also discloses intermediate UI states (editing progress, playback, id returned). However, it says nothing about permissions, latency of the editing step, or failure modes, which is what would raise this above the annotated baseline.

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?

Four short sentences, front-loaded with what the tool does and why it is safe to call, with the disambiguating caveat placed last for emphasis. Slight redundancy exists in describing the recorder returning the id and playing clips, which the output schema already covers, but nothing is padding.

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 an unusual UI-embedding tool this covers the interaction model, the deferred side effects, and the return of an id, and an output schema exists so return values need not be detailed. The gap is parameter behavior: with three optional inputs and almost no schema descriptions, an agent still cannot tell what title or instruction do from the definition alone.

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

Parameters2/5

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

Schema description coverage is only 33%: only account_id is documented in the schema, while title and instruction are bare. The description mentions none of the three parameters, so it does not compensate for the coverage gap — notably it never hints that 'instruction' steers which topics get cut into clips, which is the most consequential input here.

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 states a specific and unusual action: it renders a recorder widget inside the chat rather than performing a recording itself. The closing line 'Calling this records nothing by itself' explicitly separates it from sibling tools like add_recording, create_recording_upload, and finish_recording_upload, so an agent can route correctly without opening a schema.

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 usage context is concrete: this is the path when a user wants to capture a new video or audio take in-chat, and the flow (press record, then 'Use this recording') is spelled out. It lacks an explicit counterfactual such as 'for an existing file, use create_recording_upload instead,' so it stops short of full when/when-not guidance.

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