Skip to main content
Glama
SoManyLemons MCP

SoManyLemons MCP

Official
by NoMiddleInc

Set default recording design

set_default_recording_design
Idempotent

Set the default design for new recordings without affecting existing clips. Choose a design ID from your available recording designs to define the default for future recordings.

Instructions

Sets the design new recordings use. Existing clips are not changed.

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": {
      "design_id": "<design_id>",
      "idempotency_key": "<idempotency_key>"
    },
    "name": "set_default_recording_design"
  }
}

Input Schema

NameRequiredDescriptionDefault
design_idYesA design id from list_recording_designs.
account_idNo
idempotency_keyYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.9.36

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds one genuinely useful behavioral fact — that the change applies forward-only and does not retroactively alter existing clips — but says nothing about account scoping or how the required idempotency key behaves on retry.

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 short sentences with the primary behavior front-loaded and the scoping caveat second; nothing is redundant or padded.

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 simple mutation whose annotations already carry the safety and idempotency profile, the description covers the essential surprising behavior (no retroactive effect). However, the required idempotency_key is unexplained and there is no guidance on the multi-account parameter, leaving a real gap for a three-parameter write tool.

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%: design_id and account_id are documented in the schema, while idempotency_key has no description anywhere. The description adds no parameter meaning at all, so it fails to compensate for the uncovered required parameter.

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 ('Sets the design new recordings use') and narrows scope to future recordings, which distinguishes it from per-clip design changes. It does not name the sibling that handles existing clips, but the operation itself is unambiguous.

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?

The sentence 'Existing clips are not changed' implicitly signals that re-designing an existing recording is a different operation, but no alternative is named and no prerequisite (e.g. obtaining a design via list_recording_designs) appears in the description. Usage is implied rather than stated.

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